Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/Matt-Dionis/claude-code-configsnpx agentmods add commands/matt-dionis/claude-code-configs/analyze-usageWrote 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/matt-dionis/claude-code-configs/analyze-usage)<a href="https://agentmods.dev/commands/matt-dionis/claude-code-configs/analyze-usage"><img src="https://agentmods.dev/badge/commands/matt-dionis/claude-code-configs/analyze-usage/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/matt-dionis/claude-code-configs/analyze-usage"><img src="https://agentmods.dev/badge/commands/matt-dionis/claude-code-configs/analyze-usage.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.00021 | $0.04637 |
| Opus 5.5 | $0.00008 | $0.01855 |
| Sonnet 5.5 | $0.00004 | $0.00927 |
| Haiku 4.5 | $0.00002 | $0.00464 |
Grade A, and why
analyze-usage 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 546 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analyze TailwindCSS Usage
This command analyzes your TailwindCSS usage patterns across your codebase to identify optimization opportunities, unused utilities, and usage statistics.
What This Command Does
-
Usage Pattern Analysis
- Scans all template files for TailwindCSS class usage
- Identifies most and least used utility patterns
- Generates usage frequency reports
- Detects potential optimization opportunities
-
Bundle Size Analysis
- Analyzes generated CSS bundle size
- Identifies largest utility categories
- Compares before/after optimization results
- Tracks bundle size over time
-
Code Quality Insights
- Identifies overly complex utility combinations
- Suggests component extraction opportunities
- Detects inconsistent utility usage patterns
- Highlights potential refactoring opportunities
-
Performance Recommendations
- Suggests safelist optimizations
- Identifies unused CSS that can be purged
- Recommends content path improvements
- Provides bundle optimization suggestions
Usage Examples
Basic Usage Analysis
# Analyze utility usage in all template files
grep -r "class[Name]*=" src/ --include="*.jsx" --include="*.tsx" --include="*.vue" --include="*.html" | \
sed -E 's/.*class[Name]*=["'\''`]([^"'\''`]*)["'\''`].*/\1/' | \
tr ' ' '\n' | \
sort | uniq -c | sort -nr > tailwind-usage-report.txt
# View top 20 most used utilities
head -20 tailwind-usage-report.txt
# View least used utilities
tail -20 tailwind-usage-report.txt
Advanced Pattern Analysis
# Find all TailwindCSS classes in codebase
find src -name "*.{js,jsx,ts,tsx,vue,html}" -exec grep -l "class" {} \; | \
xargs grep -o "class[Name]*=['\"][^'\"]*['\"]" | \
sed -E 's/.*class[Name]*=["'\''`]([^"'\''`]*)["'\''`].*/\1/' | \
tr ' ' '\n' | \
grep -E '^[a-zA-Z]' | \
sort | uniq -c | sort -nr
Component Complexity Analysis
# Find components with many utility classes (potential extraction candidates)
find src/components -name "*.{jsx,tsx}" -exec sh -c '
for file do
count=$(grep -o "class[Name]*=['\"][^'\"]*['\"]" "$file" | \
sed -E "s/.*class[Name]*=[\"\'\`]([^\"\'\`]*)[\"\'\`].*/\1/" | \
tr " " "\n" | wc -l)
echo "$count $file"
done
' sh {} + | sort -nr | head -10
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.
- 1mo ago First seen · 546 lines · 21 tokens per session scan A f856f8466535
analyze-usage is a command published in the GitHub repository Matt-Dionis/claude-code-configs (619 stars, last pushed 1y ago), licensed MIT. It adds 21 tokens to every session and 4,637 once invoked, about $0.0001 per session on Opus 5.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-09-03.
Other commands, from other repositories
/a11y-audit
Auditoría de accesibilidad WCAG 2.2 completa con escaneo de HTML/componentes. Detecta: alt text faltante, problemas de contraste, navegación por teclado, etiquetas ARIA, gestión de focus, jerarquía de encabezados, etiquetas de formularios. Genera reporte accionable con instrucciones de remediación.
color-specialist
Use when colour is failing. Contrast below AA, a palette with no system behind it, dark mode that is only inverted light mode, or semantic colours that carry no meaning.
responsive-design-specialist
Use when a layout breaks between sizes. Arbitrary breakpoints, type that does not scale, images that blow out the grid, or a desktop design retrofitted onto mobile.
wcag-audit
Accessibility audit based on WCAG 2.1/2.2 and the axe-core reference.
revisar-ui
Auditoria visual retroativa de 6 pilares do código frontend implementado.
frontend-design
Read and follow the instructions in agents/frontend-design/design-all.md. Also read all referenced files in agents/frontend-design/reference/ as needed for the task.