A command that saves a confirmed security finding or useful testing pattern to persistent hunt notes.

Use it after testing to record findings in journal and pattern files and update the target’s tested endpoints and findings.

It prevents validated results and successful techniques from being lost between investigations, while recording details such as the target and endpoint.

remember — Command by Awarexone

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add commands/awarexone/agentic-bug-hunter/remember

Clone the repo

git clone --depth 1 https://github.com/Awarexone/Agentic-Bug-Hunter

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 436 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5	$0.00000	$0.00436
Opus 5	$0.00000	$0.00218
Sonnet 5	$0.00000	$0.00087
Haiku 4.5	$0.00000	$0.00044

Measured 2d ago against content hash c7de20c0cd8a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

remember scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

commands/remember.md · 63 lines

What it actually says

/remember

Save a finding or successful pattern to persistent hunt memory.

What This Does

Auto-populates fields from session context (target, endpoint, vuln_class, technique)
If /validate was run in this session, pre-fills from validation output
Prompts you to confirm or edit before saving
Writes to journal.jsonl (always) + patterns.jsonl (if confirmed + payout > 0)
Updates the target profile's tested_endpoints and findings

Usage

/remember                    # after finding something
/remember --from-validate    # explicitly pull from last /validate

Interactive Flow

REMEMBER — Log finding to hunt memory

Target:     target.com (auto-detected)
Endpoint:   /api/v2/users/{id}/orders (from session)
Vuln Class: idor (from session)
Technique:  numeric_id_swap_with_put_method

Result:     [confirmed / rejected / partial / informational]?
Severity:   [critical / high / medium / low]?
Payout:     $___?
Notes:      ___?
Tags:       [comma-separated]?

Save to hunt memory? [y/n]

Minimum Required Fields

target
vuln_class
endpoint
result

What Gets Written

Field	journal.jsonl	patterns.jsonl	target profile
Finding details	Always	If confirmed + payout > 0	findings[] updated
Tested endpoint	—	—	tested_endpoints[] updated
Tech stack	—	From target profile	—

Why This Matters

Next time you hunt a target with similar tech stack, your successful patterns are suggested first
/pickup target.com shows which endpoints you've tested and which remain
Cross-target learning: patterns from target A inform hunting on target B

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2d ago First seen · 63 lines · 0 tokens per session scan A c7de20c0cd8a

Subscribe to this mod's changes

remember is a command published in the GitHub repository Awarexone/Agentic-Bug-Hunter (4,651 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 436 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Memory and context ai-security bug-bounty bugcrowd claude-ai claude-code cti

recon

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/ / directory. Usage: /recon target.com.

elementalsouls/Claude-BugHunter · 65 tokens

hunt

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].

elementalsouls/Claude-BugHunter · 63 tokens

token-scan

Meme coin and token security scan — checks for rug pull vectors (hidden mint, honeypot, fee manipulation, LP lock bypass, authority retention, bonding curve exploits, fake renounce, sandwich amplification). Manual 8-class grep audit (with an optional automated scanner if present). Usage: /token-scan [--chain solana].

elementalsouls/Claude-BugHunter · 79 tokens

remember