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.
npx agentmods add commands/zyrexnn/cybermes/remembergit clone --depth 1 https://github.com/Zyrexnn/CybermesWhat 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.00181 |
| Opus 5 | $0.00000 | $0.00090 |
| Sonnet 5 | $0.00000 | $0.00036 |
| Haiku 4.5 | $0.00000 | $0.00018 |
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.
This is a copy
100% identical to remember — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
name: remember description: Optional manual note on a target or the last confirmed finding. Capture is automatic during autopilot; this is for extra context. Usage: /remember
/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./rememberis 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.
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 · 23 lines · 0 tokens per session scan A ebe45556fcf8
remember is a command published in the GitHub repository Zyrexnn/Cybermes (668 stars, last pushed 2d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 181 tokens. A static security scan graded it A with 0 findings. It is 100% identical to remember, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
aod.deliver
Close a completed feature with automatic documentation updates and cleanup (Triad-enhanced).
aod.project-plan
Create implementation plan with dual sign-off (PM + Architect) - Streamlined v2.
tachi.architecture
Generate an architecture description for tachi threat modeling input.
aod.roadmap
Scaffold a quarterly roadmap document from completed PRDs with PM sign-off.
aod.update
Apply upstream template updates to this adopter project.
aod.score
Re-score an existing idea's ICE rating when circumstances change.