4,341 件 ・ 関連度順
概要と使いどころ
Spin up a live local Omnigent server and exercise the GitHub Copilot SDK harness end-to-end — build copilot agents, run real turns, smoke-test, and bug-bash. Load when developing, testing, or debugging the copilot harness (omnigent/inner/copilot_executor.py, copilot_harness.py, omnigent/onboarding/copilot_auth.py) or its auth / model / tool-bridge behavior.
日本語の概要は準備中です。原文の説明を表示しています。
Spin up a live local Omnigent server and exercise the Antigravity (Gemini) SDK harness end-to-end — build antigravity agents, run real turns, smoke-test, and bug-bash. Load when developing, testing, or debugging the antigravity harness (omnigent/inner/antigravity_executor.py, antigravity_harness.py, omnigent/onboarding/antigravity_auth.py) or its auth / model / tool-bridge behavior.
日本語の概要は準備中です。原文の説明を表示しています。
Spin up a live local Omnigent server + runner and exercise the native Pi TUI harness (pi-native) end-to-end — launch the real `pi` CLI via `omnigent pi`, drive turns through the web/bridge, smoke-test, and bug-bash. Load when developing, testing, or debugging the pi-native harness (omnigent/inner/pi_native_executor.py, pi_native_harness.py, omnigent/pi_native.py, pi_native_bridge.py, pi_native_credentials.py) or its bridge / extension / auth / model behavior.
日本語の概要は準備中です。原文の説明を表示しています。
Spin up a live local Omnigent server and exercise the Cursor SDK harness end-to-end — build cursor agents, run real turns, smoke-test, and bug-bash. Load when developing, testing, or debugging the cursor harness (omnigent/inner/cursor_executor.py, cursor_harness.py, cursor_auth.py) or its auth / model / tool-bridge behavior.
日本語の概要は準備中です。原文の説明を表示しています。
Spin up a live local Omnigent server + runner and exercise the native Antigravity (agy) TUI harness (antigravity-native) end-to-end — launch the real `agy` CLI via `omnigent antigravity`, drive turns through the web UI, smoke-test, and bug-bash. Load when developing, testing, or debugging the antigravity-native harness (omnigent/inner/antigravity_native_executor.py, omnigent/antigravity_native.py, antigravity_native_bridge.py, antigravity_native_rpc.py, antigravity_native_reader.py, antigravity_native_launch.py) or its agy launch / RPC mirror / tmux delivery / OAuth / MCP-relay behavior. NOT the in-process `antigravity` Gemini SDK harness.
日本語の概要は準備中です。原文の説明を表示しています。
Decision needed + recommendation + evidence + tradeoffs, 把复杂材料压成可拍板的一页
日本語の概要は準備中です。原文の説明を表示しています。
Recover from execute_code_sandbox failures by writing code to file and executing via run_shell
日本語の概要は準備中です。原文の説明を表示しています。
Execute complex Python code via run_shell heredoc when execute_code_sandbox fails
日本語の概要は準備中です。原文の説明を表示しています。
Fallback workflow for reliable file creation and verification when automated code execution fails
日本語の概要は準備中です。原文の説明を表示しています。
Execute Python scripts from files for reliable spreadsheet operations, avoiding heredoc issues with shell_agent
日本語の概要は準備中です。原文の説明を表示しています。
Use direct Python execution for reliable spreadsheet and document/PDF generation operations
日本語の概要は準備中です。原文の説明を表示しています。
Execute Python scripts with prerequisite data validation and fallback strategies for inaccessible sources
日本語の概要は準備中です。原文の説明を表示しています。
Execute Python scripts for spreadsheets with prerequisite data validation and source accessibility checks
日本語の概要は準備中です。原文の説明を表示しています。
Debug Python script execution failures by capturing full tracebacks and verifying working directory
日本語の概要は準備中です。原文の説明を表示しています。
Fallback workflow for code execution when automated tools fail, using shell heredoc with verification
日本語の概要は準備中です。原文の説明を表示しています。
Execute Python scripts reliably using file-first approach instead of heredoc
日本語の概要は準備中です。原文の説明を表示しています。
Four-step recovery workflow for code execution failures when inline Python fails
日本語の概要は準備中です。原文の説明を表示しています。
Debug Python code execution failures by capturing partial traces, isolating failing functions, and incrementally verifying outputs
日本語の概要は準備中です。原文の説明を表示しています。
Fallback workflow for running code via file write and shell when sandbox execution fails
日本語の概要は準備中です。原文の説明を表示しています。
Fallback workflow for reliable code execution when sandbox fails repeatedly
日本語の概要は準備中です。原文の説明を表示しています。
Handle code execution failures with fallback strategies and anchored workspace paths
日本語の概要は準備中です。原文の説明を表示しています。
Fallback from execute_code_sandbox to run_shell when e2b sandbox is unavailable
日本語の概要は準備中です。原文の説明を表示しています。
Phishing campaign execution methodology for authorized red team engagements. Covers end-to-end campaign lifecycle: infrastructure provisioning (GoPhish, SMTP relay configuration, domain acquisition and aging, SPF/DKIM/DMARC alignment), payload delivery vectors (Office macro weaponization, HTA droppers, ISO/IMG container abuse, LNK shortcut hijacking, OneNote embedded payloads, HTML smuggling), email authentication bypass techniques (SPF softfail exploitation, DKIM replay attacks, display name spoofing, homoglyph and cousin domain registration), credential harvesting with MFA bypass (EvilGinx2 transparent proxy, Modlishka session relay, pixel-perfect HTML cloning), spear phishing pretext development informed by OSINT, email security gateway evasion, QR code phishing (quishing), and callback phishing for initial access. Integrates with GoPhish for campaign management, EvilGinx2 for adversary-in-the-middle credential interception, King Phisher for template design, and the Social Engineering Toolkit for payload generation. Maps to MITRE ATT&CK T1566 (Phishing) and sub-techniques T1566.001 (Spearphishing Attachment), T1566.002 (Spearphishing Link), T1566.003 (Spearphishing via Service). Assumes you have written authorization and a defined scope before any campaign execution.
日本語の概要は準備中です。原文の説明を表示しています。
Penetration test and red team report writing methodology. Covers executive summary structuring (risk-led narrative for non-technical readers), technical finding format (title, severity, affected scope, narrative, reproduction steps, impact, remediation, references), CVSS v3.1 / v4.0 scoring with vector justification, OWASP risk rating, evidence hygiene (redacting credentials, hashing client data, time-stamping every action), screenshot and PoC artifact management, finding chain narratives, scope/limitations/assumptions documentation, retest evidence and remediation tracking, deliverable formats (PDF, DOCX, HTML, JSON for SIEM ingestion), client-customer-deliverable separation, and common report mistakes (over-CVSSing, undermining the triager, missing the 'so what'). Use at the end of an engagement when authoring a deliverable, when restructuring a draft for executive readability, or when establishing a reusable report template for a consulting practice.
日本語の概要は準備中です。原文の説明を表示しています。