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 contract-testinggit 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/contract-testing)<a href="https://agentmods.dev/skills/thedaviddias/front-end-checklist/contract-testing"><img src="https://agentmods.dev/badge/skills/thedaviddias/front-end-checklist/contract-testing/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/contract-testing"><img src="https://agentmods.dev/badge/skills/thedaviddias/front-end-checklist/contract-testing.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.00038 | $0.00419 |
| Opus 5 | $0.00019 | $0.00210 |
| Sonnet 5 | $0.00008 | $0.00084 |
| Haiku 4.5 | $0.00004 | $0.00042 |
Grade A, and why
contract-testing 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 9d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 9d ago First seen · 46 lines · 38 tokens per session scan A bae0868f5aa9
contract-testing is a skill published in the GitHub repository thedaviddias/Front-End-Checklist (74,105 stars, last pushed 29d ago), with no licence file. It adds 38 tokens to every session and 419 once invoked, about $0.0002 per session on Opus 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 skills, from other repositories
add-tests
Add or update Jest unit tests for fe-tools utilities. Writes test cases, verifies coverage for common behavior, edge cases, and error inputs. Use when new functions are added, existing behavior changes, or the user asks to add tests across utils, web-utils, node-utils, canvas-utils, or ai-utils.
verify-docs-tests
Verify documentation and tests in fe-tools. Checks that exported functions have corresponding documentation and test coverage, validates JSDoc presence, and identifies missing tests. Use when the user asks to verify docs/tests, or ensure exports and docs are aligned across utils, web-utils, node-utils, canvas-utils…
test-component
Runs, analyzes, and fixes Playwright and accessibility tests for a specific DB UX component.
ship
Release — checklist-driven final verification before pushing/merging.
Dark Mode Testing Patterns
Systematic dark mode testing covering color contrast, theme switching, persistence, media query respect, component-level theming, and image adaptation.
flow-checker
Run preflight and postflight checklists against UX flows before you design and before you ship. Covers onboarding, forms, pricing, dashboards, and empty states. Returns structured findings with severity and smell linkage. Requires uxuiprinciples.com API Access (pro tier).