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/analyzegit 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.00009 | $0.00372 |
| Opus 5 | $0.00005 | $0.00186 |
| Sonnet 5 | $0.00002 | $0.00074 |
| Haiku 4.5 | $0.00001 | $0.00037 |
Grade A, and why
analyze 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
Correction Analysis
Compare before/after code content against stored rules to detect rule violations and track repeated mistakes.
When to Use
Run immediately after the user corrects your work:
- User says "no", "wrong", "not that" followed by the fix
- User edits your code and shows the corrected version
- User provides feedback that reveals a missed rule
Usage
analyze_corrections(
before_content="[original code that was wrong]",
after_content="[corrected code]"
)
What It Does
- Extracts all stored rules from memory (memory_type = "rule")
- Analyzes before_content for rule violations using trigger keywords
- Checks if after_content fixes those violations
- Logs violations to rule_violations table with frequency tracking
- Returns JSON with detected violations
Output Format
{
"status": "violations_found" | "no_violations",
"count": 3,
"violations": [
{
"rule_id": "abc123",
"rule_trigger": "before adding features",
"violation_id": "viol_xxx"
}
]
}
Related Tools
get_rule_violations()— View all tracked violationsresolve_rule_violation(violation_id)— Mark a violation as resolved/correct— Review active violations before starting work
Pattern
This implements the correction cycle from claude-memory-engine:
- User corrects you → run
/analyzeto log the mistake - Before next task → violations auto-load as reminder
- Same mistake 3+ times → consider upgrading to a hard rule
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 · 61 lines · 9 tokens per session scan A b233872122c8
analyze is a command published in the GitHub repository spideynolove/memory (3 stars, last pushed 5mo ago), licensed MIT. It adds 9 tokens to every session and 372 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。.