Front-End Checklist is a collection of front-end web development rules organized as a practical review and quality workflow for people and AI agents. Developers use it to audit projects and pull requests, check implementation details, and find guidance for remediation and verification. The catalogue entries provide skills, instructions, MCP tools, and a plugin for using the checklist in agent workflows.
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 thedaviddias/Front-End-Checklist --skill aria-command-namegit clone --depth 1 https://github.com/thedaviddias/Front-End-ChecklistWrote 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/thedaviddias/front-end-checklist/aria-command-name)<a href="https://agentmods.dev/skills/thedaviddias/front-end-checklist/aria-command-name"><img src="https://agentmods.dev/badge/skills/thedaviddias/front-end-checklist/aria-command-name/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/thedaviddias/front-end-checklist/aria-command-name"><img src="https://agentmods.dev/badge/skills/thedaviddias/front-end-checklist/aria-command-name.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00051 | $0.00365 |
| Opus 5.5 | $0.00020 | $0.00146 |
| Sonnet 5.5 | $0.00010 | $0.00073 |
| Haiku 4.5 | $0.00005 | $0.00036 |
Grade A, and why
aria-command-name 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 11d 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
Provide accessible names for ARIA command elements
Without an accessible name, screen reader users will only hear the role (e.g., 'button') without knowing what it does, making the interface impossible to navigate.
Quick Reference
- Elements with command roles (button, link, menuitem) must have a label
- Accessible names can be provided via text content,
aria-label, oraria-labelledby - Ensures users know the purpose of the interactive element
Check
Identify elements with command roles (like button or link) that lack a clear accessible name.
Fix
Add an accessible name using inner text, aria-label, or aria-labelledby to all command elements.
Explain
Explain how accessible names for command elements enable screen reader users to understand interactive controls.
Code Review
Review the rendered markup and interactive states that affect Provide accessible names for ARIA command elements. Flag exact elements, roles, labels, focus behavior, or keyboard interactions that violate the rule, and note how to verify the fix with browser accessibility tooling or assistive tech.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/rules/accessibility/aria-command-name
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago Changed aab663eddbb1
- 1mo ago First seen · 45 lines · 51 tokens per session scan A f02c1895fc19
aria-command-name is a skill published in the GitHub repository thedaviddias/Front-End-Checklist (74,476 stars, last pushed 9d ago), licensed MIT. It adds 51 tokens to every session and 365 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
scalar-design-system
Scalar's design system — design tokens, theming (@scalar/themes), CSS variables, and the @scalar/components library. Use when designing or implementing Scalar UI, especially with Paper (code-to-design / design-to-code), so output matches real Scalar tokens, colors, typography, spacing, and components instead of…
design-loop
Use when something must be built well and there is a real reference it should beat: turn what makes the reference good into measured mechanisms, then run a builder and three fresh-context critics until all three pass. Fires on 'design loop', 'make it as good as ', 'it looks generic'. NOT keeping an already-won look…
brand
Use when brand voice, visual identity, messaging frameworks, asset management, brand consistency. Activate for branded content, tone of voice, marketing assets, brand compliance, style guides.
Brand Identity Builder
Build complete brand identity systems and guidelines.
taste-bank-contribute
How to distill a frontend style from an existing project and submit it to the Taste Bank library. Covers the full contribution SOP: identity setup, sampling, packing, desensitization, and CLI submission. Invoke when the user wants to contribute/submit a new style, or distill a project's visual design into a reusable…
taste-bank
The front-end style library for coding agents. Use the taste-bank CLI to browse curated design styles (design tokens + rules + templates) and inject them into the current project. Invoke when the user wants design/style guidance, references, or to apply a saved visual style to a frontend. Commands: taste-bank list /…