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/find-unused-cssgit 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/find-unused-css)<a href="https://agentmods.dev/commands/rohitg00/awesome-claude-code-toolkit/find-unused-css"><img src="https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/find-unused-css.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.00000 | $0.00291 |
| Opus 5 | $0.00000 | $0.00146 |
| Sonnet 5 | $0.00000 | $0.00058 |
| Haiku 4.5 | $0.00000 | $0.00029 |
Grade A, and why
find-unused-css 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 2d 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
/find-unused-css - Find Unused CSS
Identify CSS rules that are not used by any component or page.
Steps
- Scan all CSS, SCSS, and styled-component files in the project
- Extract all CSS selectors: classes, IDs, element selectors, attribute selectors
- Scan all HTML, JSX, TSX, and template files for referenced CSS classes
- Check JavaScript files for dynamically applied classes (classList, className)
- Account for CSS modules by checking module import usage
- Cross-reference selectors with their usage across all template files
- Identify selectors with zero references in any template or component
- Check for CSS custom properties (variables) that are defined but never used
- Detect duplicate CSS rules with identical properties
- Calculate unused CSS as a percentage of total CSS
- Report unused selectors with file path, line number, and selector name
- Estimate bundle size savings from removing unused CSS
Rules
- Account for dynamic class generation (template literals, classnames library)
- Do not flag global reset styles or normalize.css as unused
- Check for CSS used in third-party component overrides
- Consider media query variants of the same class
- Exclude CSS-in-JS runtime styles from static analysis
- Flag utility classes only if no utility framework (Tailwind) is configured
- Report confidence level for each unused selector 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.
- 2d ago First seen · 29 lines · 0 tokens per session scan A c0ef7fd157fd
find-unused-css 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 291 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.
ci
Analyze Github Actions logs and fix issues.
two
Research & create an implementation plan with 2 approaches.
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.