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 skills add akashkendre1298/Skills --skill css-naming-auditgit clone --depth 1 https://github.com/akashkendre1298/SkillsWrote 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/skills/akashkendre1298/skills/css-naming-audit)<a href="https://agentmods.dev/skills/akashkendre1298/skills/css-naming-audit"><img src="https://agentmods.dev/badge/skills/akashkendre1298/skills/css-naming-audit/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/skills/akashkendre1298/skills/css-naming-audit"><img src="https://agentmods.dev/badge/skills/akashkendre1298/skills/css-naming-audit.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.00013 | $0.00359 |
| Opus 5.5 | $0.00005 | $0.00144 |
| Sonnet 5.5 | $0.00003 | $0.00072 |
| Haiku 4.5 | $0.00001 | $0.00036 |
Grade A, and why
css-naming-audit 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.
This is a copy
86% identical to code-smell — 30 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Use this skill when
- Working on tasks related to css naming audit
- Needing guidance, best practices, or generation for css naming audit
Do not use this skill when
- The task is unrelated to css naming audit
- You need a different domain or tool outside this scope
Instructions
- Clarify goals, constraints, and required inputs.
- Apply relevant best practices and validate outcomes.
- Provide actionable steps and verification.
Role and Execution Details: You are a CSS architecture reviewer. Audit CSS class names and structure for:
- Non-BEM class names in a BEM project (or non-utility in a Tailwind project)
- Classes named by appearance not purpose (red-text, big-button, left-panel)
- Classes with no current usage in the codebase (dead CSS)
- Duplicate rules for the same visual property
- Specificity wars (!important usage, ID selectors in component CSS)
- Global styles leaking into component scope
- Inconsistent naming convention across components
Output: a list of issues with current name → recommended name, plus a CSS refactor for each.
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
- Ensure all security, privacy, and compliance guidelines are followed.
- The instructions provided are guidelines and should be adapted to the specific context of the codebase or project.
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 · 43 lines · 13 tokens per session scan A e25e4296bce1
css-naming-audit is a skill published in the GitHub repository akashkendre1298/Skills (5 stars, last pushed 5mo ago), licensed MIT. It adds 13 tokens to every session and 359 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 86% identical to code-smell, differing in 30 lines, and is treated as a copy.
Other skills, from other repositories
review-animations
Reviews animation and motion code against a high craft bar derived from Emil Kowalski's design engineering philosophy. Default to flagging; approval is earned.
ring:validating-ux-completeness
Validating that UX specifications are complete before technical design: a read-only checklist over wireframes, states, responsive behavior, accessibility, and component-library alignment, emitting a DESIGN VALIDATED / NEEDS REVISION verdict to design-validation.md. Standalone utility — run after a product-designer…
a11y-audit
Run a Maestro-style accessibility audit for WCAG compliance, ARIA usage, keyboard navigation, and screen reader compatibility.
seo-audit
Run a Maestro-style SEO assessment for meta tags, structured data, crawlability, and Core Web Vitals.
generic-static-code-reviewer
Review static site code for bugs, security issues, performance problems, accessibility gaps, and CLAUDE.md compliance. Enforces pure HTML/CSS/JS standards, minimal page weight, mobile-first design. Use when completing features, before commits, or reviewing changes.
web-standards-reviewer
Review an existing web project for web-standards use and essential dependencies only, against the rules of /web-conventions, /javascript-conventions, and the stack skill the project composes (web-static, web-sprinkles, web-components), and answer with the shortest possible feedback — one line per finding, one line…