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/thisisyoyodev/claude-rag/reviewgit clone --depth 1 https://github.com/ThisisYoYoDev/claude-ragWhat 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.00019 | $0.00290 |
| Opus 5 | $0.00010 | $0.00145 |
| Sonnet 5 | $0.00004 | $0.00058 |
| Haiku 4.5 | $0.00002 | $0.00029 |
Grade A, and why
review 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
RAG Review
Review the current work: "$ARGUMENTS"
Steps
- Understand what changed: Read the current git diff or recent files to understand what was modified
- Search for past issues: Use
searchandcode_searchto find:- Past errors in the same files or areas
- Previous bug fixes that might be affected
- Related discussions or decisions
- Check file history: Use
code_historyon modified files to see past patterns - Expand relevant findings: Use
detailto read full context of concerning past events
Output format
Write a review with:
- Changes summary: what was modified
- Past context: relevant history for each changed area
- ⚠️ Warnings: potential issues based on past experience
- ✅ Looks good: areas that follow established patterns
- 💡 Suggestions: improvements based on past learnings
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 · 28 lines · 19 tokens per session scan A a53b00cd658d
review is a command published in the GitHub repository ThisisYoYoDev/claude-rag (9 stars, last pushed 5mo ago), licensed MIT. It adds 19 tokens to every session and 290 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-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.