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/correctgit 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.00294 |
| Opus 5 | $0.00003 | $0.00147 |
| Sonnet 5 | $0.00001 | $0.00059 |
| Haiku 4.5 | $0.00001 | $0.00029 |
Grade A, and why
correct 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
Review Rule Violations
Display all tracked rule violations from the correction analysis system.
When to Use
- Before starting a new task (automatic reminder)
- After running
/reflectto see what was cleaned up - Manually anytime with
/correct
Usage
get_rule_violations(unresolved_only=true)
What It Shows
- Rule violations detected by
/analyze - Frequency count (how many times each rule was missed)
- Rule content that was violated
- Detection timestamp
Output Format
{
"count": 2,
"violations": [
{
"id": "viol_xxx",
"rule_id": "abc123",
"violation_type": "rule_miss",
"rule_content": "Gather evidence before...",
"frequency": 3,
"detected_at": "2026-03-24T10:30:00",
"resolved": false
}
]
}
Resolving Violions
resolve_rule_violation(violation_id="viol_xxx")
Integration with Workflow
- Make mistake → User corrects you
- Run
/analyzeto log the violation - Before next task →
/correctshows active violations - Internalize rule → Mark as resolved
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 · 59 lines · 7 tokens per session scan A 57f5e2e9d972
correct 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 294 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。.