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 find-npm-packagesgit 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/find-npm-packages)<a href="https://agentmods.dev/skills/thedaviddias/front-end-checklist/find-npm-packages"><img src="https://agentmods.dev/badge/skills/thedaviddias/front-end-checklist/find-npm-packages/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/find-npm-packages"><img src="https://agentmods.dev/badge/skills/thedaviddias/front-end-checklist/find-npm-packages.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Data Exfiltration · line 70 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00048 | $0.00942 |
| Opus 5.5 | $0.00019 | $0.00377 |
| Sonnet 5.5 | $0.00010 | $0.00188 |
| Haiku 4.5 | $0.00005 | $0.00094 |
Grade A, and why
find-npm-packages scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl https://registry.npmjs.org/{package}/latest | jq '{name, version, description}' How it starts
The opening of the file, as written. The whole thing — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
find-npm-packages
Identify, validate, and add npm package references to a Front-End Checklist rule.
What this skill does
Given a rule file or rule slug, this skill will:
- Understand what the rule is checking for
- Research which npm packages are commonly used to implement, automate, or enforce the rule
- Validate each candidate against quality thresholds (popularity + maintenance)
- Select the best 2–3 packages
- Add them to the rule's
npmPackagesfrontmatter field
Quality thresholds (mandatory — do not skip)
Before selecting any package, check it against these criteria using the npm registry:
| Criterion | Minimum |
|---|---|
| Weekly downloads | >10,000/week |
| Last publish | Within 18 months |
| npm registry | Must be listed (registry.npmjs.org/{name}) |
Packages that fail any threshold must be excluded, regardless of how relevant they are.
Research steps
Step 1 — Understand the rule
Read the rule file: packages/content/rules/en/{category}/{slug}.mdx
Focus on:
- What problem does this rule solve?
- What technique, spec, or behavior does it enforce?
- What tools or linters are mentioned in the
tools:field?
Step 2 — Identify candidates
Search for packages that:
- Detect the issue (linters, audit tools, CLI scanners)
- Fix or implement the pattern (frameworks, utilities, polyfills)
- Test for compliance (test utilities, CI integrations)
Use https://www.npmjs.com/search?q={keywords} and knowledge of the ecosystem to find candidates.
Prefer packages that are:
- Part of the official toolchain (e.g.,
eslint,stylelint, official plugins) - Widely adopted across the industry
- Actively maintained (recent commits, open issues responded to)
Step 3 — Validate each candidate
For each candidate package, fetch and verify:
# Metadata
curl https://registry.npmjs.org/{package}/latest | jq '{name, version, description}'
# Weekly downloads
curl https://api.npmjs.org/downloads/point/last-week/{package} | jq '.downloads'
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 · 126 lines · 48 tokens per session scan A 72f53fe78798
find-npm-packages is a skill published in the GitHub repository thedaviddias/Front-End-Checklist (74,577 stars, last pushed 21d ago), licensed MIT. It adds 48 tokens to every session and 942 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
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…
citation-verification
This skill provides reference guidance for citation verification in academic writing. Use when the user asks about "citation verification best practices", "how to verify references", "preventing fake citations", or needs guidance on citation accuracy. This skill supports ml-paper-writing by providing detailed…
stopovers
Per-program stopover rules for award redemptions. Which programs allow free stopovers, how many, how long, and which don't. Covers Icelandair, Aeroplan, Alaska, Flying Blue, Singapore, Cathay, JAL, and the negative space (BA, AA, Delta).
flight-search-strategy
Canonical multi-source flight search strategy. Source priority (Duffel, Ignav, Google Flights, Skiplagged, Kiwi, Seats.aero, Southwest), parallel workflow, market selection for international price arbitrage.
alliances
Airline alliance membership (Star Alliance, oneworld, SkyTeam) and cross-alliance booking relationships. Maps which loyalty programs book which airlines, including bilateral partnerships outside alliances.
lingtai-tui-anatomy
Source-navigation guide for the LingTai Go monorepo that ships lingtai-tui and lingtai-portal. Read this for TUI/Portal structure, runtime-boundary evidence, exact Go ownership, or when updating an ANATOMY.md. The repository-root ANATOMY.md is normative; this skill routes into that graph without duplicating it. Kernel…