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/a11y-scangit 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/a11y-scan)<a href="https://agentmods.dev/commands/rohitg00/awesome-claude-code-toolkit/a11y-scan"><img src="https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/a11y-scan.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.00018 | $0.00475 |
| Opus 5 | $0.00009 | $0.00237 |
| Sonnet 5 | $0.00004 | $0.00095 |
| Haiku 4.5 | $0.00002 | $0.00047 |
Grade A, and why
a11y-scan 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 6d 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
Scan web application components for accessibility violations against WCAG guidelines.
Steps
- Identify the target: component file, page, or entire project.
- Scan for common WCAG 2.1 violations:
- Perceivable: Images without alt text, videos without captions, low color contrast.
- Operable: Non-keyboard-accessible elements, missing focus indicators, no skip links.
- Understandable: Missing form labels, no error descriptions, inconsistent navigation.
- Robust: Invalid HTML, missing ARIA roles, incorrect heading hierarchy.
- Check component-level issues:
- Interactive elements (buttons, links) without accessible names.
- Custom components missing ARIA roles and states.
- Dynamic content updates without live region announcements.
- Modal dialogs without focus trapping.
- Check form accessibility:
- Labels associated with inputs via
htmlFor/idor wrapping. - Error messages linked to inputs via
aria-describedby. - Required fields marked with
aria-required.
- Labels associated with inputs via
- Classify findings by WCAG level (A, AA, AAA) and severity.
- Provide specific fix instructions for each violation.
Format
Accessibility Scan: <scope>
Violations: <N> (A: <n>, AA: <n>, AAA: <n>)
WCAG A (must fix):
- <file>:<line> - <element> missing alt text (1.1.1)
- <file>:<line> - <element> not keyboard accessible (2.1.1)
WCAG AA (should fix):
- <file>:<line> - contrast ratio 3.2:1, needs 4.5:1 (1.4.3)
Passing:
- Heading hierarchy is correct
- Language attribute is set
Rules
- Prioritize WCAG A violations (legal compliance baseline).
- Provide the specific WCAG criterion number for each violation.
- Include fix code snippets, not just descriptions.
- Check both static HTML/JSX and dynamically generated content.
- Test with screen reader considerations (not just automated rules).
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.
- 6d ago First seen · 54 lines · 18 tokens per session scan A 09f82456df5c
a11y-scan 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 18 tokens to every session and 475 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-08-30.
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.
checklist
Generate a custom checklist for the current feature based on user requirements.