remember
The /remember command saves vulnerability findings and successful hunting patterns to persistent memory by logging details to journal.jsonl and optionally patterns.jsonl files. Use it after discovering a vulnerability to auto-populate from session context or prior /validate output, then confirm severity and payout information so future hunts on similar targets can leverage successful techniques.
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/elementalsouls/Claude-BugHunter/HEAD/commands/remember.md -o ~/.claude/commands/remember.mdremember.md
# /remember > **Capture is automatic.** During an engine/autopilot run, every confirmed finding is > written to the ledger (`~/.claude/bughunter/memory/findings.jsonl`) with no action from you. > `/remember` is only for adding an **optional manual note** — a technique detail or > follow-up idea — that the automatic capture would not include. ## Usage ``` /remember # then describe the note; it is appended to the target's rollup ``` ## What It Is Not This is no longer the primary way findings enter memory — the engine captures those deterministically. Use it sparingly for human context.
Run autonomous hunt loop on a target — scope check → recon → rank surface → hunt → validate → report with configurable checkpoints. Usage: /autopilot target.com [--paranoid|--normal|--yolo]
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
Active vulnerability hunting. Two-track dispatcher — asks Red Team vs WAPT, hands off to hunt-dispatch skill and sibling commands. Usage: /hunt target.com | /hunt *.target.com | /hunt targets.txt [--vuln-class X] [--source-code P] [--chrome]
On-demand intelligence fetch for a target — CVEs, disclosed reports, new features. Pulls NVD/GitHub-Advisory CVEs + bundled disclosed reports + hunt memory context. Usage: /intel target.com
Inspect or rotate the autopilot ledger JSONL files (findings.jsonl, negatives.jsonl). Caps file size and keeps N rotated backups so memory does not grow unbounded.
Pick up a previous hunt on a target — shows hunt history and untested surface from the autopilot ledger. Usage: /pickup target.com
Run full recon pipeline on a target — subdomain enum (Chaos API + subfinder), live host discovery (dnsx + httpx), URL crawl (katana + waybackurls + gau), gf pattern classification, nuclei scan. Outputs to recon/<target>/ directory. Usage: /recon target.com
Write a submission-ready bug bounty report. Generates H1/Bugcrowd/Intigriti/Immunefi format with CVSS 3.1 score, proof of concept, impact statement, and remediation. Run /validate first. Usage: /report