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/helloruru/claude-memory-engine/analyzegit clone --depth 1 https://github.com/HelloRuru/claude-memory-engineWhat 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.00010 | $0.00293 |
| Opus 5 | $0.00005 | $0.00147 |
| Sonnet 5 | $0.00002 | $0.00059 |
| Haiku 4.5 | $0.00001 | $0.00029 |
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 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
/analyze — Record Corrections
Compare the user's edits against your output. Find what you got wrong and why.
Steps
- Find the diff — Identify what the user changed in your output (text, code, structure, tone)
- Check against rules — Compare each correction against existing rules in CLAUDE.md, memory files, and learned skills
- Log missed rules — If a rule exists but you didn't follow it, log it with a count (e.g., "2nd time missing this")
- Distill new patterns — If the correction doesn't match any existing rule, distill it into a new one
- Save to error notebook — Append to
~/.claude/skills/learned/writing-review-list.md(or project-specific file) - Report — Tell the user: "Logged N corrections. M were known rules I missed, K are new patterns."
Error notebook format
### Rule name
- **Rule:** What to do
- **Missed:** N times
- **Status:** active / cleared
- **Example:** What went wrong → what was correct
When to run
Run this right after the user corrects your work. The fresher the context, the better the analysis.
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 · 31 lines · 10 tokens per session scan A af97a85c9914
analyze is a command published in the GitHub repository HelloRuru/claude-memory-engine (133 stars, last pushed 3mo ago), licensed MIT. It adds 10 tokens to every session and 293 once invoked, about $0.0001 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
awesome-docs
Generate, convert, and maintain animated GitHub-safe Markdown documents with animated SVG diagrams. Covers four SVG patterns (architecture flow, lifecycle loop, field carousel, timeline phases), guided interview for any doc type (README, architecture guide, runbook, API reference, tutorial, RFC, post-mortem…
grill-me
Run an interactive one-question-at-a-time oral drill for research defence or active-recall study, escalating around weak answers and ending with a study sheet. Use when the user asks to be grilled, quizzed, or prepared for a viva, job talk, seminar, or exam. Not for a written critique; use $devils-advocate or a review…
brief-compliance-check
Check a LaTeX coursework submission against the requirements in a supplied PDF assessment brief. Use when verifying format, required sections, word limits, or deliverables before submission. Not for general prose proofreading; use $proofread.
init-project-course
Bootstrap a university course or module folder with the canonical teaching structure, guidance, and starter files. Use when creating or migrating a course workspace. Not for checking an existing course without modifying it; use $audit-project-course.
init-project-light
Bootstrap a lightweight project with minimal guidance, context, and repository structure. Use when a small non-research project needs durable AI collaboration without the full research or course scaffold. Not for formal research projects; use $init-project-research.
resume_handoff
Resume work from handoff document with context analysis and validation.