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/mnemehq/mneme/recordgit clone --depth 1 https://github.com/MnemeHQ/mnemeWhat 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.00008 | $0.00265 |
| Opus 5 | $0.00004 | $0.00133 |
| Sonnet 5 | $0.00002 | $0.00053 |
| Haiku 4.5 | $0.00001 | $0.00026 |
Grade A, and why
record 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- mneme-record — 100% identical, 0 lines differ
What it actually says
Ask the user for:
id— snake_case identifier (e.g.auth_001)decision— one sentence stating the decisionrationale— why this decision was madescope— list of keywords describing where this applies (used for retrieval — choose words that will appear in file names or task descriptions)constraints— list of prohibited approachesanti_patterns— list of specific strings/tokens to flag as violations
Then run via the Bash tool:
mneme add_decision \
--memory .mneme/project_memory.json \
--id <id> \
--decision "<...>" \
--rationale "<...>" \
[--scope <keyword> ...] \
[--constraint "<...>" ...] \
[--anti-pattern "<...>" ...]
Confirm with:
mneme list_decisions --memory .mneme/project_memory.json
Scope tip: Choose scope keywords that will appear in file paths or task descriptions where this decision applies. The hook query is derived from the target file name — scope tokens that overlap with file names ensure the decision is retrieved during enforcement.
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 · 34 lines · 8 tokens per session scan A 69aee8655b15
record is a command published in the GitHub repository MnemeHQ/mneme (19 stars, last pushed 2d ago), licensed MIT. It adds 8 tokens to every session and 265 once invoked, about $0.0000 per session on Opus 5. 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.
Other commands, from other repositories
icpg-bootstrap
Infer ReasonNodes from existing git commit history. One-time setup for existing codebases.
version
Display current guide and Claude Code versions.
go-review
Go code review for idiomatic patterns.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
session-report
Capture what changed this session and why, scoped to the current branch. Read by ship verbs when synthesizing the commit message; deleted after a successful commit.
execute
Executa o plano aprovado em .first-plan/07-state/plans/. Segue o plano à risca, para se algo invalidar premissa, gera relatório ao final.