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/plangit 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.00020 | $0.00343 |
| Opus 5 | $0.00010 | $0.00171 |
| Sonnet 5 | $0.00004 | $0.00069 |
| Haiku 4.5 | $0.00002 | $0.00034 |
Grade A, and why
plan 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-Informed Plan
Create a plan for: "$ARGUMENTS"
Steps
-
Search history: Use
searchto find past sessions related to this task. Look for:- Similar tasks that were done before
- Errors or bugs encountered in related code
- Patterns that worked well
-
Check code history: Use
code_searchandcode_historyto find:- Files that will likely be touched
- Past modifications and their outcomes
- Known issues in those areas
-
Expand relevant results: Use
detailorturnto read full context of the most relevant past events -
Generate the plan incorporating lessons learned:
- What to do (step by step)
- What to watch out for (based on past errors)
- Which files to modify (based on history)
- Which patterns to reuse (based on past successes)
Output format
Write a numbered plan with:
- Each step clearly described
- Warnings from past sessions marked with ⚠️
- Reusable patterns marked with ✅
- File paths that will need changes
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 · 37 lines · 20 tokens per session scan A 9b0fb1376a9d
plan is a command published in the GitHub repository ThisisYoYoDev/claude-rag (9 stars, last pushed 5mo ago), licensed MIT. It adds 20 tokens to every session and 343 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.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.