MoonMcp: Skill for Claude Code

Orchestrating MoonMCP + Strix

You drive two complementary offensive tools that are both exposed to you over MCP — you never leave your agent (opencode / hermes / Claude):

• MoonMCP — fast, cheap, scope-first recon & detection. Maps the attack surface and finds leads (headers, IDOR signals, injection reflections, takeovers, secrets, redirects, GraphQL, desync indicators). Deterministic, stdlib, rate-limited, refuses out-of-scope targets.
• Strix — an autonomous AI pentester in a Docker sandbox that proves a lead by generating a working PoC (Caido proxy + browser + exploit runtime). Powerful but heavy: it runs its own LLM loop, costs real tokens/time, and exploits — so you delegate to it deliberately, not reflexively.

Think of it as: MoonMCP finds, Strix confirms.

The pipeline (find → decide → validate → merge)

1. Recon & detect with MoonMCP (cheap first). Use the operator prompts already built in (bug_bounty_operator, deep_recon, injection_hunt): set scope_add / a program, sweep passive → light active, and collect leads with add_finding. Confirm what you can cheaply inside MoonMCP — differential passive_scan, http_repeater, intruder, and blind-vuln oast_* callbacks.

2. Decide what deserves Strix. Only delegate leads that are (a) in scope, (b) high-value (RCE/SSRF/IDOR/auth/injection/logic), and (c) not already confirmed or refuted cheaply. Do not send Strix "test everything" — hand it a focused, evidence-backed task.

3. Delegate to Strix as a tool. Call the Strix tool (e.g. strix_run) with:

   • the exact in-scope target,
   • a tight instruction that carries the rules of engagement and the concrete lead(s) MoonMCP found (see the instruction recipe below).

   strix_run defaults to watch=True: it opens a terminal window that streams Strix's live output (falling back to a tmux session, then a tail -f hint on headless boxes) so the operator can watch the autonomous run in real time. The result's live_console says how it opened; MOONMCP_TERMINAL forces a specific emulator, watch=False disables the window.

4. Consume & merge. Take Strix's validated findings + PoCs, record them with MoonMCP add_finding (severity + evidence), then triage_findings to dedupe and rank, and report / export_findings for the writeup. Strix's PoC is your "confirmed" gate; a MoonMCP lead Strix could not reproduce stays unconfirmed.