/remember
Log a finding or pattern to persistent brain memory. Auto-fills from session context. Usage: /remember
$ npx -y skills add H-mmer/pentest-agents --skill remember --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/remember
Context preview
The summary Claude sees to decide when to auto-load this skill.
Log a finding or pattern to persistent brain memory. Auto-fills from session context. Usage: /remember
SKILL.md
remember.SKILL.mdname: remember
description: "Log a finding or pattern to persistent brain memory. Auto-fills from session context. Usage: /remember"
disable-model-invocation: false
Save current finding/pattern to brain memory.
Flow
1. Read current session context — what target, endpoint, vuln class 2. Ask user to confirm or edit:
- Target: (auto-detected)
- Endpoint: (from session)
- Vuln class: (from session)
- Result: confirmed / rejected / partial
- Severity: critical / high / medium / low
- Bounty: $___
- Notes: ___
3. Write to brain:
- If confirmed: `uv run python3 $CLAUDE_PROJECT_DIR/tools/brain.py record <target> confirmed "<description>" "<details>"`
- If rejected: `uv run python3 $CLAUDE_PROJECT_DIR/tools/brain.py record <target> exhausted "<what failed>" "<why>"`
4. Sync to global brain: `uv run python3 $CLAUDE_PROJECT_DIR/tools/global_brain.py learn technique "<pattern>"` 5. Track response if submitted: `uv run python3 $CLAUDE_PROJECT_DIR/tools/response_tracker.py log <id> <status>`
Why This Matters
- /resume shows which endpoints you've tested and which remain
- Cross-target learning: patterns from target A inform hunting on target B
- Global brain accumulates technique knowledge across all engagements
Top-Tier Recall Standard
Before writing memory, make it useful to a future agent that has no conversation context.
Use this shape:
target:
surface:
vuln_class:
primitive:
accounts_or_roles:
evidence_path:
request_summary:
response_marker:
impact:
status:
next_action:
If the item is rejected, preserve the blocker with the same care as a finding. High-quality negative memory prevents duplicate work and false confidence.
Read more
name: remember description: "Log a finding or pattern to persistent brain memory. Auto-fills from session context. Usage: /remember" disable-model-invocation: false
Save current finding/pattern to brain memory.
Flow
1. Read current session context — what target, endpoint, vuln class 2. Ask user to confirm or edit:
- Target: (auto-detected)
- Endpoint: (from session)
- Vuln class: (from session)
- Result: confirmed / rejected / partial
- Severity: critical / high / medium / low
- Bounty: $___
- Notes: ___
3. Write to brain:
- If confirmed: `uv run python3 $CLAUDE_PROJECT_DIR/tools/brain.py record <target> confirmed "<description>" "<details>"`
- If rejected: `uv run python3 $CLAUDE_PROJECT_DIR/tools/brain.py record <target> exhausted "<what failed>" "<why>"`
4. Sync to global brain: `uv run python3 $CLAUDE_PROJECT_DIR/tools/global_brain.py learn technique "<pattern>"` 5. Track response if submitted: `uv run python3 $CLAUDE_PROJECT_DIR/tools/response_tracker.py log <id> <status>`
Why This Matters
- /resume shows which endpoints you've tested and which remain
- Cross-target learning: patterns from target A inform hunting on target B
- Global brain accumulates technique knowledge across all engagements
Top-Tier Recall Standard
Before writing memory, make it useful to a future agent that has no conversation context.
Use this shape:
target: surface: vuln_class: primitive: accounts_or_roles: evidence_path: request_summary: response_marker: impact: status: next_action:
If the item is rejected, preserve the blocker with the same care as a finding. High-quality negative memory prevents duplicate work and false confidence.
Bug bounty agent framework for Claude Code, Codex, Gemini, Cursor, Windsurf, Copilot, and OpenClaw — 48 agents, 26 commands, 19 CLI tools, 2 MCP servers, autonomous hunt loops, exploit chain builder.
Repo: H-mmer/pentest-agents
Other skills on pentest-agents.
- /analyze
Analyze recon output with AI to suggest high-value targets and attack strategies. Usage: /analyze <target>
Open skill - /autopilot
Autonomous hunt orchestrator. INSATIABLE in --autonomous mode: enforces an EXHAUSTION CONTRACT (26 canonical hunter classes, surface probe A-I, depth-engine ≥25 attempts/class, wall-clock floor 90 min/target, PRE-COMPLETION GATE before any summary). No early stops, no clarifying
Open skill - /brain
Manage the engagement brain. Subcommands: 'init' to set up, 'brief <target>' for pre-flight, 'status' for overview, 'exhausted [target]' to see dead ends.
Open skill - /chain
Build deep exploit chains — dispatches chain-builder agent. Given bug A, recursively walks the chain graph. Usage: /chain (then describe bug A)
Open skill - /correlate
Run the finding correlation engine to discover attack chains from individual findings.
Open skill - /cost
Show cost tracking and ROI for this engagement.
Open skill

