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/suggest-colors)<a href="https://agentmods.dev/commands/rohitg00/awesome-claude-code-toolkit/suggest-colors"><img src="https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/suggest-colors/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/suggest-colors"><img src="https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/suggest-colors.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.00294 |
| Opus 5.5 | $0.00000 | $0.00118 |
| Sonnet 5.5 | $0.00000 | $0.00059 |
| Haiku 4.5 | $0.00000 | $0.00029 |
Grade A, and why
suggest-colors 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
/suggest-colors - Suggest Accessible Colors
Suggest alternative colors that meet WCAG contrast requirements.
Steps
- Identify the failing color pairs from the contrast audit
- For each failing pair, determine the target ratio: 4.5:1 (AA normal) or 3:1 (AA large)
- Calculate the minimum adjustment needed to meet the target ratio
- Generate color alternatives by adjusting lightness while preserving hue and saturation
- Provide at least 3 alternative colors for each failing pair
- Verify each suggestion meets the target contrast ratio
- Check that suggested colors fit within the project's design system palette
- Show color swatches (hex codes) with their contrast ratios
- Suggest pairing options: darkening the foreground vs lightening the background
- Verify suggested colors also work for color-blind users (deuteranopia, protanopia)
- Generate a CSS variable override file with the accessible alternatives
- Present before/after comparison showing the visual difference
Rules
- Prefer minimal color changes to maintain the design intent
- Suggest colors that stay within the same hue family
- Provide options for both adjusting foreground and background
- Check suggestions against the full color palette for consistency
- Verify suggestions work for all color blindness types
- Do not suggest pure black/white unless the design already uses them
- Include the exact hex/RGB values for easy implementation
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 42cbfb2c98fc
suggest-colors 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 294 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
design
Full design pipeline for a web or web-app target: brief → tokens → generation → motion → review. Use /design:mobile for iOS/Android instead.
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.