Awesome Claude Code Toolkit is a curated collection of extensions and configuration for Claude Code, including agents, skills, commands, plugins, hooks, rules, templates, MCP configurations, and companion apps. It is for Claude Code users who want ready-made workflows and integrations for different development tasks. The catalogue add-ons are selected components from this toolkit.
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/rohitg00/awesome-claude-code-toolkit/update-depsgit clone --depth 1 https://github.com/rohitg00/awesome-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/rohitg00/awesome-claude-code-toolkit/update-deps)<a href="https://agentmods.dev/commands/rohitg00/awesome-claude-code-toolkit/update-deps"><img src="https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/update-deps.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.1 | $0.00013 | $0.00344 |
| Opus 5 | $0.00006 | $0.00172 |
| Sonnet 5 | $0.00003 | $0.00069 |
| Haiku 4.5 | $0.00001 | $0.00034 |
Grade A, and why
update-deps 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
Safely update project dependencies with compatibility verification.
Steps
- List all outdated dependencies:
npm outdated,pip list --outdated. - Categorize updates by risk:
- Patch: Bug fixes, safe to auto-update.
- Minor: New features, backward compatible.
- Major: Breaking changes, requires review.
- For each update candidate:
- Read the changelog for breaking changes.
- Check peer dependency compatibility.
- Verify TypeScript type compatibility if applicable.
- Apply updates in order: patch first, then minor, then major.
- After each batch, run the test suite.
- If tests fail, identify the breaking dependency and provide fix guidance.
- Update lock file and commit changes.
Format
Dependency Updates Applied:
Patch (safe):
- <pkg> 1.0.0 -> 1.0.1
Minor (compatible):
- <pkg> 1.0.0 -> 1.1.0
Major (breaking - review required):
- <pkg> 1.0.0 -> 2.0.0: <breaking change summary>
Tests: <pass/fail after updates>
Rules
- Never update major versions without reading the changelog first.
- Run tests after each update category, not just at the end.
- Commit patch and minor updates separately from major updates.
- Do not update dev dependencies and production dependencies in the same batch.
- Keep a rollback plan: note the exact versions before updating.
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 · 48 lines · 13 tokens per session scan A 6e305f24a014
update-deps is a command published in the GitHub repository rohitg00/awesome-claude-code-toolkit (2,587 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 13 tokens to every session and 344 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-09-03.
Other commands, from other repositories
create-prompt
Create a new prompt that another Claude can execute.
design
Command "design" from laborany/laborany, covering /ppt-design 命令 - 风格设计, 命令说明, 触发方式, 执行流程 and step 1: 展示风格选择菜单.
brainstorm
You are a Solution Brainstormer, an elite software engineering expert who specializes in system architecture design and technical decision-making. Your core mission is to collaborate with users to find the best possible solutions while maintaining brutal honesty about feasibility and trade-offs.
enhance
Analyze the current copy issues and enhance it.
ci
Analyze Github Actions logs and fix issues.
config
Adjust Claude Code status line display (preset, sections, bar width).