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/memory-gcgit 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.00040 | $0.00313 |
| Opus 5 | $0.00020 | $0.00156 |
| Sonnet 5 | $0.00008 | $0.00063 |
| Haiku 4.5 | $0.00004 | $0.00031 |
Grade A, and why
memory-gc 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 3d 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 memory-gc — 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
/memory-gc
Garbage-collect the autopilot ledger (~/.claude/bughunter/memory/). Reports current sizes, rotates oversized files past a configurable cap, or purges old backups.
Usage
/memory-gc # report only
/memory-gc --rotate # rotate files above 10 MB (default cap)
/memory-gc --rotate --max-mb 5 # custom cap
/memory-gc --purge-backups # delete all .1/.2/.3 backups
/memory-gc --dir <path> # scan a non-default ledger dir
Implementation
The agent shells out to, from the repo root:
python3 engine/memory.py --gc [--rotate] [--purge-backups] [--dir PATH] [--max-mb N]
Defaults
- Rotation cap: 10 MB per file · Backups kept: 3 (
<file>.1newest →<file>.3oldest) - Scope: every
*.jsonlunder the ledger dir (findings.jsonl,negatives.jsonl)
Rotation also fires automatically on append inside the ledger writer, so files stay bounded without any session-end hook.
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.
- 3d ago First seen · 34 lines · 40 tokens per session scan A 9e056ee5352f
memory-gc is a command published in the GitHub repository Zyrexnn/Cybermes (668 stars, last pushed 3d ago), licensed Apache-2.0. It adds 40 tokens to every session and 313 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to memory-gc, 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.spec
Create feature specification with automatic PM sign-off - Streamlined v2.
aod.tasks
Generate tasks with triple sign-off (PM + Architect + Team-Lead) - Streamlined v2.
aod.document
Quality review — code simplification, docstrings, CHANGELOG, API docs (supports --autonomous).
tachi.architecture
Generate an architecture description for tachi threat modeling input.
aod.run
Run the full AOD lifecycle orchestrator — chains all 6 stages (Discover → Define → Plan → Build → Deliver → Document) with session-resilient state and governance gates at every boundary.