autopilot
The `/autopilot` command executes a fully autonomous security testing workflow against a target domain, progressing through scope validation, reconnaissance, attack surface ranking, vulnerability hunting, validation gates, and report generation without requiring approval between steps. Use this when you need rapid, comprehensive vulnerability scanning with deterministic scope safety and built-in checkpoints for review, choosing between paranoid mode (full stops), normal mode (batch checkpoints), or yolo mode (minimal approvals) depending on testing velocity and token budget requirements.
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/elementalsouls/Claude-BugHunter/HEAD/commands/autopilot.md -o ~/.claude/commands/autopilot.mdautopilot.md
# /autopilot Autonomous hunt loop with deterministic scope safety and configurable checkpoints. ## Usage ``` /autopilot target.com # default: --paranoid mode /autopilot target.com --normal # batch checkpoint after validation /autopilot target.com --yolo # minimal checkpoints (still requires report approval) /autopilot target.com --quick # fast surface scan, fewer checks, lower token use /autopilot targets.txt # multiple targets — one domain per line in the file ``` ## Session Isolation (Important) **Start a fresh Claude Code session per target.** Claude accumulates context across a session — testing multiple targets in one session causes cross-contamination where findings, payloads, and tech stack assumptions from target A bleed into target B. Best practice: ```bash # Terminal 1: target A claude → /autopilot targetA.com # Terminal 2: target B (separate process) claude → /autopilot targetB.com ``` If you must test multiple targets in one session, run `/pickup target.com` at the start of each target switch to reload the correct context. ## Token Optimization Use `--quick` for faster, lower-cost scans (skips deep fuzzing and extended nuclei templates): ``` /autopilot target.com --quick # ~40% fewer tokens, covers main attack surface /hunt target.com --vuln-class idor # single bug class — lowest token use ``` For long hunts, run `/compact` (Claude Code built-in) periodically to compress context without losing findings. ## What This Does Runs the full hunt cycle without stopping for approval at each step: ``` 1. SCOPE Load and confirm program scope 2. RECON Run recon (or use cached if < 7 days old) 3. RANK Prioritize attack surface (recon-ranker agent) 4. HUNT Test P1 endpoints systematically 5. VALIDATE 7-Question Gate on findings 6. REPORT Draft reports for validated findings 7. CHECKPOINT Present to human for review ``` ## Safety Guarantees - **Every URL** is checked against the scope allowlist before any request - **Reports are NEVER auto-submitted** — always requires explicit approval - **PUT/DELETE/PATCH** require human approval in --yolo mode (safe methods only) - **Circuit breaker** stops hammering if 5 consecutive 403/429/timeout on same host - **Rate limited** at 1 req/sec (testing) and 10 req/sec (recon) ## Checkpoint Modes | Mode | When it stops | Best for | |---|---|---| | `--paranoid` | Every finding + partial signal | New targets, learning the surface | | `--normal` | After validation batch | Systematic coverage | | `--yolo` | After full surface exhausted | Familiar targets, experienced hunters | ## Ledger memory (token saving) The autonomous loop can consult the **autopilot ledger** to skip provably-wasteful agent calls — an item already **confirmed** on a prior run (carried forward, not re-tested) or a vuln_class with strong **negative** history on this tech stack (`dead-class`). - **`--paranoid` (default) / `--normal`:** memory is **off** — full coverage, no skips. - **`--quick` / `--yolo`:** the command passes `--use-memory` to the engine — skips on. - A vuln_class never hunted on this stack is **never** skipped, and every skip is logged (`hunt: skipped via ledger (...)`). Coverage is never silently reduced. - Capture is automatic; the ledger fills itself as you run. Manage size with `/memory-gc`. ## After Autopilot - Run `/remember` to log successful patterns to hunt memory - Run `/pickup target.com` next time to pick up where you left off - Check the ledger (`~/.claude/bughunter/memory/findings.jsonl`) or run `/memory-gc` for its size
End-to-end Android APK red-team pipeline — automated APK acquisition (Play Store + apkpure + apkmirror fallback), jadx decompilation, secret/URL/JWT/Firebase grep, pinned-cert extraction, exported-component enumeration, Frida runtime instrumentation templates, intent-injection probes. Built from an authorized external red-team engagement where 7 APKs were pulled manually, 4 download attempts truncated, and a hardcoded JWT + 30 internal API endpoints were recovered from one of the apps. Use when target has a mobile app catalogue (Play Store developer page), when you find an APK URL hosted on a web server, or when post-recon mentions "mobile app" in scope.
Local-tooling companion to the bug-bounty orchestrator — carries the SAME complete bug-bounty workflow, but reach for THIS variant when you also need to resolve where tools, wordlists, and clones are installed on the local machine (jhaddix, SecLists, trufflehog, ffuf, dalfox, ghauri); for pure orchestration/routing use the bug-bounty skill. Workflow it covers — recon (subdomain enumeration, asset discovery, fingerprinting, HackerOne scope, source code audit), pre-hunt learning (disclosed reports, tech stack research, mind maps, threat modeling), vulnerability hunting (IDOR, SSRF, XSS, auth bypass, CSRF, race conditions, SQLi, XXE, file upload, business logic, GraphQL, HTTP smuggling, cache poisoning, OAuth, timing side-channels, OIDC, SSTI, subdomain takeover, cloud misconfig, ATO chains, agentic AI), LLM/AI security testing (chatbot IDOR, prompt injection, indirect injection, ASCII smuggling, exfil channels, RCE via code tools, system prompt extraction, ASI01-ASI10), A-to-B bug chaining (IDOR→auth bypass, SSRF→cloud metadata, XSS→ATO, open redirect→OAuth theft, S3→bundle→secret→OAuth), bypass tables (SSRF IP bypass, open redirect bypass, file upload bypass), language-specific grep (JS prototype pollution, Python pickle, PHP type juggling, Go template.HTML, Ruby YAML.load, Rust unwrap), and reporting (7-Question Gate, 4 validation gates, human-tone writing, templates by vuln class, CVSS 3.1, PoC generation, always-rejected list, conditional chain table, submission checklist). Use when you need the local install path of a tool / wordlist / clone for a hunt, or as the full-workflow variant when operating from this local toolkit; for general routing use the bug-bounty skill. 中文触发词：漏洞赏金、安全测试、渗透测试、漏洞挖掘、信息收集、子域名枚举、XSS测试、SQL注入、SSRF、安全审计、漏洞报告
Use at the START of any bug bounty hunting session, when switching targets, or when feeling lost about what to do next. Master orchestrator that combines the 5-phase non-linear hunting workflow with the critical thinking framework (developer psychology, anomaly detection, What-If experiments). Routes to all other skills based on current hunting phase. Also use when asking "what should I do next" or "where am I in the process.
Complete bug bounty workflow — recon (subdomain enumeration, asset discovery, fingerprinting, HackerOne scope, source code audit), pre-hunt learning (disclosed reports, tech stack research, mind maps, threat modeling), vulnerability hunting (IDOR, SSRF, XSS, auth bypass, CSRF, race conditions, SQLi, XXE, file upload, business logic, GraphQL, HTTP smuggling, cache poisoning, OAuth, timing side-channels, OIDC, SSTI, subdomain takeover, cloud misconfig, ATO chains, agentic AI), LLM/AI security testing (chatbot IDOR, prompt injection, indirect injection, ASCII smuggling, exfil channels, RCE via code tools, system prompt extraction, ASI01-ASI10), A-to-B bug chaining (IDOR→auth bypass, SSRF→cloud metadata, XSS→ATO, open redirect→OAuth theft, S3→bundle→secret→OAuth), bypass tables (SSRF IP bypass, open redirect bypass, file upload bypass), language-specific grep (JS prototype pollution, Python pickle, PHP type juggling, Go template.HTML, Ruby YAML.load, Rust unwrap), and reporting (7-Question Gate, 4 validation gates, human-tone writing, templates by vuln class, CVSS 3.1, PoC generation, always-rejected list, conditional chain table, submission checklist). Use for ANY bug bounty task — starting a new target, doing recon, hunting specific vulns, auditing source code, testing AI features, validating findings, or writing reports. 中文触发词：漏洞赏金、安全测试、渗透测试、漏洞挖掘、信息收集、子域名枚举、XSS测试、SQL注入、SSRF、安全审计、漏洞报告
Bugcrowd-specific reporting tactics complementing report-writing: VRT category search-and-fallback strategy when no exact match exists, manual severity override when VRT defaults underrate impact, severity-request paragraph as first body section, OOS-clause rebuttal templates (rate limiting on auth-flow endpoints, debug-info framing, user-enumeration with sensitive PII, theoretical-issue counter), chained-finding cross-reference patterns, target selection for QA-vs-prod programs, researcher-side hygiene (Bugcrowdninja email alias, account state restoration, friendly-tester posture). Use when filing a Bugcrowd submission, when VRT default seems wrong, when triager closes as OOS or downgrades severity, when chaining linked submissions, or when scope distinguishes production from QA. Pairs with report-writing and triage-validation.
Build an exploit chain — given bug A, finds B and C to combine for higher severity and payout. Knows common chain patterns: IDOR→ATO, SSRF→cloud metadata, XSS→ATO, open redirect→OAuth theft, S3→bundle→secret→OAuth. Usage: /chain
Cloud IAM red-team attack chain across AWS, Azure, GCP — focused on EXTERNAL exploitation paths and post-credential-discovery privilege analysis. Covers IAM enumeration (aws iam, az role, gcloud iam), STS/AssumeRole chaining, Azure Managed Identity abuse (via SSRF/leak), GCP service account JSON abuse, IMDSv1/v2 attacks via SSRF, K8s ServiceAccount token privilege analysis once held (token discovery / cluster exposure is owned by hunt-k8s), role-trust-policy confused-deputy, cross-account assume-role enumeration, IAM privilege escalation patterns (24+ AWS, 8+ Azure, 6+ GCP), and AWS Cognito Identity Pool unauthenticated-role attack chain (GetId → GetCredentialsForIdentity → IAM role abuse). Built for the case where recon yields a credential (key, JSON, token) and you need to know what it grants and how to escalate. Use when an AWS key / Azure secret / GCP service account JSON / K8s SA token surfaces from a code repo, JS bundle, APK, breach corpus, or SSRF chain.
External SSL VPN / remote-access appliance attack matrix — Cisco ASA/AnyConnect, Fortinet FortiGate/FortiOS, Citrix NetScaler/ADC, Palo Alto GlobalProtect, Pulse Secure / Ivanti Connect Secure, SonicWall, F5 Big-IP. Covers version fingerprinting, CVE matrix (2018-2026), AAA backend identification, default credentials, configuration-disclosure paths, pre-auth RCE/SSRF/path-traversal exploits where applicable. Built from authorized-engagement Cisco ASA testing plus 2024-2026 enterprise VPN CVE landscape. Use whenever the target's perimeter exposes any SSL VPN appliance or remote-access gateway — these are the most common initial-access points in 2024-2026 actor TTPs.