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.
git 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/code-migrate)<a href="https://agentmods.dev/commands/rohitg00/awesome-claude-code-toolkit/code-migrate"><img src="https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/code-migrate/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/rohitg00/awesome-claude-code-toolkit/code-migrate"><img src="https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/code-migrate.svg" alt="Reviewed on agentmods" width="80" 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.00019 | $0.00355 |
| Opus 5 | $0.00010 | $0.00178 |
| Sonnet 5 | $0.00004 | $0.00071 |
| Haiku 4.5 | $0.00002 | $0.00036 |
Grade A, and why
code-migrate 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 5d 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
Migrate code from one framework version, library, or pattern to another.
Steps
- Identify the migration scope:
- Framework upgrade (React 17 to 18, Next.js 13 to 14, Django 4 to 5).
- Library replacement (Moment to Day.js, Express to Fastify).
- Pattern change (class components to hooks, callbacks to async/await).
- Research breaking changes and migration guides for the target version.
- Scan the codebase for affected patterns:
- Deprecated API usage.
- Changed import paths.
- Removed features needing alternatives.
- Generate a migration plan with ordered steps.
- Apply changes file by file:
- Update imports and require statements.
- Refactor deprecated patterns to new equivalents.
- Update configuration files.
- Update type definitions if applicable.
- Update
package.jsonor equivalent with new versions. - Run tests after each major change to catch regressions early.
Format
Migration: <from> -> <to>
Files affected: <N>
Changes:
- <pattern>: <N> occurrences updated
- <import>: <N> files updated
Breaking changes handled:
- <change>: <how it was resolved>
Verification: tests <pass/fail>
Rules
- Apply changes incrementally, not all at once.
- Run tests after each change category to isolate regressions.
- Keep a log of all changes for review.
- Do not upgrade transitive dependencies without testing compatibility.
- Preserve existing functionality; migration should be behavior-preserving.
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.
- 5d ago First seen · 51 lines · 19 tokens per session scan A 4a74c3a8c762
code-migrate is a command published in the GitHub repository rohitg00/awesome-claude-code-toolkit (2,598 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 19 tokens to every session and 355 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
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.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.