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/run-audit)<a href="https://agentmods.dev/commands/rohitg00/awesome-claude-code-toolkit/run-audit"><img src="https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/run-audit/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/run-audit"><img src="https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/run-audit.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.00000 | $0.00313 |
| Opus 5.5 | $0.00000 | $0.00125 |
| Sonnet 5.5 | $0.00000 | $0.00063 |
| Haiku 4.5 | $0.00000 | $0.00031 |
Grade A, and why
run-audit 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 2mo 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
/run-audit - Run Accessibility Audit
Execute a comprehensive accessibility audit against WCAG guidelines.
Steps
- Ask the user for the target URL or component to audit
- Configure the audit scope: WCAG 2.1 Level A, AA, or AAA
- Run automated accessibility scanning using axe-core or similar engine
- Check all WCAG success criteria applicable to the content type
- Test keyboard navigation: all interactive elements reachable and operable
- Verify focus management: visible focus indicators, logical focus order
- Check ARIA usage: proper roles, states, properties, and landmark regions
- Validate heading hierarchy: logical order without skipping levels
- Test color contrast ratios: 4.5:1 for normal text, 3:1 for large text
- Check form accessibility: labels, error messages, required field indicators
- Verify media accessibility: alt text, captions, audio descriptions
- Compile findings into a prioritized report by impact level
Rules
- Test against WCAG 2.1 AA as the minimum standard
- Automated tools catch about 30% of issues; note that manual testing is also needed
- Prioritize issues by user impact: critical (blocks access), serious, moderate, minor
- Include WCAG success criterion reference for each finding
- Test with actual assistive technology when possible (VoiceOver, NVDA)
- Do not flag decorative images that correctly have empty alt attributes
- Include remediation guidance with each finding
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.
- 2mo ago First seen · 29 lines · 0 tokens per session scan A 2a8b0add0b1f
run-audit is a command published in the GitHub repository rohitg00/awesome-claude-code-toolkit (2,810 stars, last pushed 5mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 313 tokens. 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-08-30.
Other commands, from other repositories
design
A command for choosing or defining the visual style of a PowerPoint presentation, including its colors, fonts, and page layouts. It offers preset styles, custom brand settings, and recommendations based on the presentation topic.
start-design-plan
Start collaborative design process with brainstorming and planning.
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.