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 Eliyce/paqad-ai --skill component-conformance-reviewgit clone --depth 1 https://github.com/Eliyce/paqad-aiWrote 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/eliyce/paqad-ai/component-conformance-review)<a href="https://agentmods.dev/skills/eliyce/paqad-ai/component-conformance-review"><img src="https://agentmods.dev/badge/skills/eliyce/paqad-ai/component-conformance-review/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/eliyce/paqad-ai/component-conformance-review"><img src="https://agentmods.dev/badge/skills/eliyce/paqad-ai/component-conformance-review.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.00037 | $0.00850 |
| Opus 5 | $0.00018 | $0.00425 |
| Sonnet 5 | $0.00007 | $0.00170 |
| Haiku 4.5 | $0.00004 | $0.00085 |
Grade A, and why
component-conformance-review 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 8d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What It Does
Audits the project's UI components against components.md. The AST-derived component inventory is the subject; the contract is the standard. Every component used in source must appear in components.md with declared variants, states, and permitted compositions. Override sprawl (!important, inline style=, undocumented Tailwind combinations, shadcn primitives wrapped without spec) is a finding.
Use This When
Use this for every design-test run, after token-conformance-review. The two together form the "is the contract followed at the source level" pair.
Inputs
- Read
docs/instructions/design-system/components.md. - Read the contract-summary from
design-system-coverage(declared component clauses). - Read
references/component-conformance-checklist.mdbefore scanning.
Procedure
The set difference between source and contract is deterministic — drive it with the scripts. Reserve LLM judgment for severity and the "is this primitive correctly wrapped" question.
- Run
scripts/derive-inventory.sh [components-dir]→<name>\t<source-file>TSV. The script already excludes tests, stories, type decls, barrels, and lower-case helpers. - Run
scripts/parse-components-md.sh <components.md>→<name>\t<variants-csv>\t<states-csv>TSV. Empty CSV slots are-. - Run
scripts/diff-inventories.sh --source <derived> --declared <parsed>. Each row is a deterministic gap:in-source-not-declared\tName\t<file>→documentation-driftfinding, medium.declared-not-in-source\tName\t-→documentation-driftfinding (contract references a non-existent component), medium to high depending on whether the contract is what the team intends to build.
- Run
runtime/scripts/design/scan-overrides.shto enumerate!important, inlinestyle=, arbitrary Tailwind brackets, undocumented utility combos. The LLM decides whether each hit is a missing prop on a declared component or genuine code smell. - For each declared component, verify its declared variants are implemented in the source file. Missing variant →
componentfinding, high.
What ships with it
7 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.
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.
- 8d ago First seen · 73 lines · 37 tokens per session scan A 7f38a8d1ba40
component-conformance-review is a skill published in the GitHub repository Eliyce/paqad-ai (8 stars, last pushed today), licensed MIT. It adds 37 tokens to every session and 850 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
make-interfaces-feel-better
Use when building or reviewing UI polish: typography, hit areas, nested radius, optical alignment, shadows, media outlines, micro-interactions, and animation performance.
frontend-skill
Use when the task asks for a visually strong landing page, website, app, prototype, demo, or game UI. This skill enforces restrained composition, image-led hierarchy, cohesive content structure, and tasteful motion while avoiding generic cards, weak branding, and UI clutter.
frontend-design
Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Use whenever the task produces or modifies anything a user will see rendered — websites, landing pages, web apps, dashboards, React/HTML/Vue components, artifacts with visual output, style overhauls, or "make this…
frontend-design
Produce intentional, responsive, accessible UI work and perform visual QA instead of generic component assembly.
designlang-tokens
Use when styling UI for cal.com — references the extracted design system tokens instead of inventing colors, spacing, or typography.
accessibility-a11y
Semantic HTML, keyboard navigation, focus states, ARIA labels, skip links, and WCAG contrast requirements. Use when ensuring accessibility compliance, implementing keyboard navigation, or adding screen reader support.