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/logingit 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.00016 | $0.00271 |
| Opus 5 | $0.00008 | $0.00135 |
| Sonnet 5 | $0.00003 | $0.00054 |
| Haiku 4.5 | $0.00002 | $0.00027 |
Grade B, and why
login scanned grade B with 2 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.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
curl -s -X POST "https://api.clauderag.io/api/v1/auth/login" -H "Content-Type: application/json" -d '{"email":"<email>"}' Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -X POST "https://api.clauderag.io/api/v1/auth/login" -H "Content-Type: application/json" -d '{"email":"<email>"}' What it actually says
Login to Claude RAG
Detect email: !echo "EMAIL:$(git config --global user.email 2>/dev/null || echo 'NONE')"
Instructions
-
Confirm email with AskUserQuestion.
-
Send magic link:
curl -s -X POST "https://api.clauderag.io/api/v1/auth/login" -H "Content-Type: application/json" -d '{"email":"<email>"}'If error "No account found" → tell user to run
/claude-rag:setup. Save thetokenfrom response. -
Ask for 6-digit code with AskUserQuestion.
-
Verify:
bash "${CLAUDE_PLUGIN_ROOT}/scripts/verify.sh" "<email>" "<code>"Or check magic link:
bash "${CLAUDE_PLUGIN_ROOT}/scripts/check.sh" "<email>" "<token>" -
Save API key:
bash "${CLAUDE_PLUGIN_ROOT}/scripts/save-config.sh" "<api_key>" -
Confirm success.
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 · 38 lines · 16 tokens per session scan B bcda5ed1fd75
login is a command published in the GitHub repository ThisisYoYoDev/claude-rag (9 stars, last pushed 5mo ago), licensed MIT. It adds 16 tokens to every session and 271 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 2 findings (sends data to an external url, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
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.