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/setupgit 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.00017 | $0.00375 |
| Opus 5 | $0.00009 | $0.00187 |
| Sonnet 5 | $0.00003 | $0.00075 |
| Haiku 4.5 | $0.00002 | $0.00038 |
Grade B, and why
setup scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
Detect email and config: !`echo "EMAIL:$(git config --global user.email 2>/dev/null || echo 'NONE')" && echo "CONFIG:$(cat ~/.claude/plugins/claude-rag/config.json 2>/dev/null || echo 'NO_CONFIG')"` What it actually says
Setup Claude RAG
Detect email and config: !echo "EMAIL:$(git config --global user.email 2>/dev/null || echo 'NONE')" && echo "CONFIG:$(cat ~/.claude/plugins/claude-rag/config.json 2>/dev/null || echo 'NO_CONFIG')"
Instructions
-
If CONFIG already has an apiKey, tell user they're set up and verify with
mcp__plugin_claude-rag_rag__health. Ask to reconfigure. If no → stop. -
Confirm email with AskUserQuestion (auto-detected above).
-
Register — run this script with the email and name:
bash "${CLAUDE_PLUGIN_ROOT}/scripts/setup.sh" "<email>" "<name>"Parse output for
TOKEN:andSTEP:email_sent:. -
Tell user to check email. Ask for code with AskUserQuestion.
-
Verify code — run:
bash "${CLAUDE_PLUGIN_ROOT}/scripts/verify.sh" "<email>" "<code>"If failed, try checking magic link:
bash "${CLAUDE_PLUGIN_ROOT}/scripts/check.sh" "<email>" "<token>" -
Save config with the API key:
bash "${CLAUDE_PLUGIN_ROOT}/scripts/save-config.sh" "<api_key>" -
Test with
mcp__plugin_claude-rag_rag__health. -
Show success + commands list. Remind to restart Claude Code.
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 · 41 lines · 17 tokens per session scan B 8d727eb19a69
setup is a command published in the GitHub repository ThisisYoYoDev/claude-rag (9 stars, last pushed 5mo ago), licensed MIT. It adds 17 tokens to every session and 375 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). 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.