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/sergei-aronsen/claude-code-toolkit/update-toolkitgit clone --depth 1 https://github.com/sergei-aronsen/claude-code-toolkitWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/sergei-aronsen/claude-code-toolkit/update-toolkit)<a href="https://agentmods.dev/commands/sergei-aronsen/claude-code-toolkit/update-toolkit"><img src="https://agentmods.dev/badge/commands/sergei-aronsen/claude-code-toolkit/update-toolkit.svg" alt="Measured on agentmods" height="20"></a>What 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.00000 | $0.00878 |
| Opus 5 | $0.00000 | $0.00439 |
| Sonnet 5 | $0.00000 | $0.00176 |
| Haiku 4.5 | $0.00000 | $0.00088 |
Grade D, and why
update-toolkit scanned grade D with 3 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 3d 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.
cat .claude/.toolkit-version Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
# Move current .claude aside (NEVER `rm -rf .claude` — keep it as a recovery point) Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s https://raw.githubusercontent.com/sergei-aronsen/claude-code-toolkit/main/manifest.json | grep version How it starts
The opening of the file, as written. The whole thing — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/update-toolkit — Update Claude Code Toolkit
Purpose
Smart update of Claude Code Toolkit — updates system files while preserving your customizations.
Usage
/update-toolkit
What Gets Updated
| Category | Files | Behavior |
|---|---|---|
| Agents | agents/*.md |
Always updated |
| Prompts | prompts/*.md |
Always updated |
| Skills | skills/ai-models/SKILL.md |
Always updated |
| CLAUDE.md | Main instructions | Smart merge (see below) |
What Gets Preserved
| Category | Files | Behavior |
|---|---|---|
| User sections in CLAUDE.md | Project Overview, Structure, Commands, Notes | Preserved during merge |
| Settings | settings.json, settings.local.json |
Never touched |
| Memory | memory/*.md, memory/*.json |
Never overwritten |
| Skill rules | skills/skill-rules.json |
Never overwritten |
| Scratchpad | scratchpad/* |
Never touched |
Smart Merge for CLAUDE.md
The update script identifies two types of sections:
System sections (updated):
- Compact Instructions
- Workflow Rules, Plan Mode, Git Workflow
- Security Rules, Architecture Guidelines
- Available Agents, Commands, Audits, Skills
User sections (preserved):
- 🎯 Project Overview
- 📁 Project Structure
- ⚡ Essential Commands
- ⚠️ Project-Specific Notes
Process
1. Detect framework (Laravel, Next.js, etc.)
2. Download manifest.json (version info)
3. Create backup (.claude-backup-YYYYMMDD-HHMMSS/)
4. Update agents, prompts, skills
5. Smart merge CLAUDE.md:
- Download new template
- Extract user sections from current file
- Replace system sections with new versions
- Restore user sections
6. Save version to .toolkit-version
7. Show changelog link
Version Tracking
# Check current version
cat .claude/.toolkit-version
# Compare with remote
curl -s https://raw.githubusercontent.com/sergei-aronsen/claude-code-toolkit/main/manifest.json | grep version
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.
- 3d ago First seen · 120 lines · 0 tokens per session scan D c6d41f02513e
update-toolkit is a command published in the GitHub repository sergei-aronsen/claude-code-toolkit (5 stars, last pushed 17d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 878 tokens. A static security scan graded it D with 3 findings (reads agent configuration directories, recursive force delete, 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.