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/check-contrastgit 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/check-contrast)<a href="https://agentmods.dev/commands/rohitg00/awesome-claude-code-toolkit/check-contrast"><img src="https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/check-contrast.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.00320 |
| Opus 5 | $0.00000 | $0.00160 |
| Sonnet 5 | $0.00000 | $0.00064 |
| Haiku 4.5 | $0.00000 | $0.00032 |
Grade A, and why
check-contrast 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 yesterday.
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
/check-contrast - Check Color Contrast
Check color contrast ratios against WCAG accessibility requirements.
Steps
- Scan CSS, SCSS, and styled-components for all text color and background color pairs
- Resolve CSS custom properties and theme variables to actual color values
- Calculate the luminance contrast ratio for each foreground/background pair
- Check against WCAG 2.1 requirements: 4.5:1 for normal text, 3:1 for large text (18px+ or 14px+ bold)
- Check non-text contrast for UI components and graphical objects: 3:1 ratio
- Identify text on images or gradients that may have insufficient contrast
- Check focus indicator contrast against adjacent colors
- Verify contrast in both light and dark themes if the app supports them
- Flag transparent or semi-transparent colors that reduce effective contrast
- Generate a report: element, foreground color, background color, ratio, pass/fail
- Show the total pass/fail count and compliance percentage
- Highlight the worst offenders that need immediate attention
Rules
- Test both light and dark mode color schemes
- Account for opacity when calculating effective contrast
- Large text threshold: 18px regular or 14px bold
- Do not flag disabled elements as they are exempt from contrast requirements
- Check placeholder text contrast (should meet 4.5:1 even though many sites skip this)
- Consider adjacent color contrast for interactive component boundaries
- Report all unique color pairs, not every instance
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.
- yesterday First seen · 29 lines · 0 tokens per session scan A 7ac8a84fac24
check-contrast 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 costs nothing until one of its globs matches a file; then it loads 320 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-09-03.
Other commands, from other repositories
screenshot
Create a design based on screenshot.
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.
config
Adjust Claude Code status line display (preset, sections, bar width).
ci
Analyze Github Actions logs and fix issues.
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.