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/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.00255 |
| Opus 5 | $0.00003 | $0.00128 |
| Sonnet 5 | $0.00001 | $0.00051 |
| Haiku 4.5 | $0.00001 | $0.00026 |
Grade A, and why
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 yesterday.
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
Memory Health Check
Quick daily scan to check the memory system's health and capacity.
Usage
No parameters needed. Just run:
get_database_info()
What It Checks
- Database file size and location
- Session count
- Memory count
- Collection count
- Package APIs discovered
- Codebase patterns stored
- Validation checks performed
- Tool errors tracked
- Rule violations tracked
Output Format
{
"database_path": "/path/to/memory.db",
"project_path": "/path/to/project",
"sessions_count": 5,
"memories_count": 42,
"collections_count": 3,
"package_apis_count": 15,
"codebase_patterns_count": 28,
"validation_checks_count": 7,
"database_size": 245760
}
When to Run
- Daily as a quick health scan
- After major work sessions
- When memory behavior seems off
- Before
/reflectto understand current state
Related
/full-check— Weekly comprehensive audit/check— Daily quick scan (this command)
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.
- yesterday First seen · 56 lines · 7 tokens per session scan A f4168371b03f
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 255 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。.