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 cligit 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/cli)<a href="https://agentmods.dev/skills/thedaviddias/front-end-checklist/cli"><img src="https://agentmods.dev/badge/skills/thedaviddias/front-end-checklist/cli/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/cli"><img src="https://agentmods.dev/badge/skills/thedaviddias/front-end-checklist/cli.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.00096 | $0.00694 |
| Opus 5.5 | $0.00038 | $0.00278 |
| Sonnet 5.5 | $0.00019 | $0.00139 |
| Haiku 4.5 | $0.00010 | $0.00069 |
Grade A, and why
frontendchecklist 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 15d 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Front-End Checklist CLI
frontendchecklist checks frontend code against the Front-End Checklist rules. It works offline,
prints JSON when its output is piped (which is how you will usually call it), and uses exit codes
you can branch on.
Run it with npx -y @frontendchecklist/cli <command> if frontendchecklist is not installed.
When to use it
- After writing or editing frontend files:
frontendchecklist review <paths>. - Before committing:
git diff --cached | frontendchecklist review -. - When the user asks to audit a deployed page:
frontendchecklist audit https://.... - When you need the authoritative guidance for a topic:
frontendchecklist search <topic>, thenfrontendchecklist rule <slug>. - For a structured pass (launch, accessibility, SEO, performance):
frontendchecklist checklists, thenfrontendchecklist checklist <slug>.
Commands
| Command | Purpose |
|---|---|
review <paths...|-> |
Static review of files, directories (walked; vendor dirs skipped), or stdin |
audit <https-url> |
Fetch a public page and review its HTML |
search [query] [--focus a,b] [-n 10] |
Find rules by keyword, technology, or category |
rule <slug> |
Why a rule matters, how to check it, how to fix it |
checklists / checklist <slug> |
Curated checklists and their rules |
categories |
Categories with rule counts |
schema |
Full command reference as JSON |
Useful flags: --focus accessibility,seo, --min-priority high, --fail-on high.
Reading results
reviewandauditreturn{ findings: [{ target, rule, title, priority, issue, fix? }], failing }.- Exit code
0: fine.1: findings at or above--fail-on.2: bad input or runtime error, with{ "error": "..." }on stdout. - Findings are conservative static heuristics. "No findings" means nothing provable was found, not
that the code is clean: follow up with
search/rulefor areas the heuristics cannot see (rendered contrast, focus order, real performance).
What ships with it
14 files 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.
- .gitignore 6 B
- package.json 1.5 KB
- README.md 2.4 KB
- scripts/build.ts 1.9 KB runs code
- src/args.ts 5.5 KB runs code
- src/commands/audit.ts 2.8 KB runs code
- src/commands/lookup.ts 5.0 KB runs code
- src/commands/review.ts 3.9 KB runs code
- src/content.ts 1.5 KB runs code
- src/index.ts 2.9 KB runs code
- src/output.ts 3.3 KB runs code
- src/spec.ts 5.1 KB runs code
- tests/cli.test.mjs 4.6 KB runs code
- tsconfig.json 202 B
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.
- 15d ago First seen · 53 lines · 96 tokens per session scan A 699424dff350
frontendchecklist is a skill published in the GitHub repository thedaviddias/Front-End-Checklist (74,479 stars, last pushed 11d ago), licensed MIT. It adds 96 tokens to every session and 694 once invoked, about $0.0004 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-10-02.
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…
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 /…
pw-admin-ui
Use when designing, structuring, or rendering HTML for ProcessWire Admin interfaces, custom Process modules, or Inputfields.
bulma
Bulma reference tool. Use when working with bulma in frontend contexts.
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
visual-ralph
Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ultragoal with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.