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/zayne-sprague/dr-claude-code/updategit clone --depth 1 https://github.com/Zayne-sprague/Dr-Claude-CodeWhat 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.00030 | $0.00364 |
| Opus 5 | $0.00015 | $0.00182 |
| Sonnet 5 | $0.00006 | $0.00073 |
| Haiku 4.5 | $0.00003 | $0.00036 |
Grade C, and why
update scanned grade C 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
curl -fsSL https://raw.githubusercontent.com/Zayne-sprague/Dr-Claude-Code/main/update.sh | bash Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -fsSL https://raw.githubusercontent.com/Zayne-sprague/Dr-Claude-Code/main/update.sh | bash What it actually says
RACA Update
Update RACA to the latest version by running the update script.
Step 1: Find the workspace
Determine the workspace root (check RACA_WORKSPACE env, or walk up from cwd looking for .raca/). Store the absolute path.
Step 2: Run the update
bash $WS/raca-update.sh
If raca-update.sh doesn't exist (older install), run it directly:
curl -fsSL https://raw.githubusercontent.com/Zayne-sprague/Dr-Claude-Code/main/update.sh | bash
Step 3: Report
Tell the user what happened:
"RACA updated! Your experiments, notes, API keys, and cluster config are untouched. New skills, rules, and tools have been pulled in."
If the update script reported any warnings or errors, relay them.
Step 4: Handle conflicts
If the update script reports files that were "modified by you and skipped", those are config files the user customized. RACA chose not to overwrite them.
For each conflicted file:
- Read the user's current version
- Fetch the latest RACA version (
curlthe raw file from GitHub, or read from.raca-repoif still around) - Show the user a summary of what changed on each side
- Propose a merged version that preserves the user's customizations while incorporating RACA's updates
- Apply with user approval
If there are no conflicts, skip this step.
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 · 46 lines · 30 tokens per session scan C 7b81d56a86ff
update is a command published in the GitHub repository Zayne-sprague/Dr-Claude-Code (5 stars, last pushed 5mo ago), licensed MIT. It adds 30 tokens to every session and 364 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, 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.