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/spideynolove/memory/full-checkgit clone --depth 1 https://github.com/spideynolove/memoryWhat 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.00007 | $0.00299 |
| Opus 5 | $0.00003 | $0.00150 |
| Sonnet 5 | $0.00001 | $0.00060 |
| Haiku 4.5 | $0.00001 | $0.00030 |
Grade A, and why
full-check 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.
What it actually says
Full Memory Audit
Comprehensive weekly audit of the entire memory system.
Usage
Run multiple checks in sequence:
get_database_info()
get_frequent_errors(min_frequency=3)
get_rule_violations(unresolved_only=true)
get_attention_state()
What It Checks
- Database Info — All tables, sizes, counts
- Frequent Tool Errors — Tools failing 3+ times
- Unresolved Violations — Rules being missed repeatedly
- Attention State — Memory attention patterns
Interpreting Results
- Frequent errors → Tools or patterns needing attention
- High violation count → Rules not being internalized
- Large database → Consider
/reflectto clean up - Skewed attention → Some memories getting too much/little focus
When to Run
- Weekly as comprehensive audit
- Before major cleanup sessions
- When investigating system issues
- After big feature additions
Actions to Take
Based on findings:
- High violation frequency → Review rule triggers
- Many frequent errors → Check tool usage patterns
- Large database → Run
/reflectto consolidate - Low attention on key rules → Use
boost_memory_attention()
Related
/check— Daily quick scan/reflect— Clean up and consolidate memories
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 · 53 lines · 7 tokens per session scan A 0092b9815120
full-check is a command published in the GitHub repository spideynolove/memory (3 stars, last pushed 5mo ago), licensed MIT. It adds 7 tokens to every session and 299 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-31.
Other commands, from other repositories
handoff
Update memory-bank/handoff.md to pause or switch models.
save-context
Write a phase-completion summary and update the Memory Bank.
start-task
Plan a task with minimal context before coding.
add-project
在 Obsidian vault 里新增一个项目。自动检测 vault（不存在则 inline 初始化）、分析代码结构生成架构草稿、写入 CLAUDE.md。通常是接触新项目时唯一需要运行的命令。.
update-memory
全量对账 Code ↔ Obsidian ↔ auto-memory 三方，找漂移并让用户逐项决定如何修。地图 vs 地形原则的工程兜底。.
commit
智能 git 提交：自动生成 commit message、提交代码、然后调用 /sync-docs 同步到 Obsidian。.