design-system-coverage

design-system-coverage is a skill for Codex from Eliyce/paqad-ai. It costs 31 tokens per session (916 once invoked), scanned A, original, MIT.

A design-system documentation review skill that checks whether the project's rules for tokens, components, accessibility, motion, responsive behavior, and interface patterns are complete. It produces a coverage inventory that later design checks can use.

In plain words
What is it for?
Use it as the first step in a design-test workflow to assess the design-system documentation and decide whether further checks can proceed.
Why use it?
Downstream UI reviews are less reliable when the project has no clear design rules to compare against. This identifies missing or incomplete documentation before those reviews run.

Skill for Codex

Written for Codex: agents/openai.yaml present.

Good fit Use it as the first step in a design-test workflow to assess the design-system documentation and decide whether further checks can proceed.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/eliyce/paqad-ai/design-system-coverage
Install

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.

Any agent
npx skills add Eliyce/paqad-ai --skill design-system-coverage
Clone the repo
git clone --depth 1 https://github.com/Eliyce/paqad-ai

Made for: Codex.

Wrote 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.

agentmods badge for design-system-coverage

README.md
[![agentmods](https://agentmods.dev/badge/skills/eliyce/paqad-ai/design-system-coverage/github.svg)](https://agentmods.dev/skills/eliyce/paqad-ai/design-system-coverage)
Your own site
<a href="https://agentmods.dev/skills/eliyce/paqad-ai/design-system-coverage"><img src="https://agentmods.dev/badge/skills/eliyce/paqad-ai/design-system-coverage/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.

agentmods 80×15 button for design-system-coverage

Your own site · 80×15
<a href="https://agentmods.dev/skills/eliyce/paqad-ai/design-system-coverage"><img src="https://agentmods.dev/badge/skills/eliyce/paqad-ai/design-system-coverage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 916 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00031 $0.00916
Opus 5 $0.00015 $0.00458
Sonnet 5 $0.00006 $0.00183
Haiku 4.5 $0.00003 $0.00092

Measured 9d ago against content hash 9a3d954e3e98, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

design-system-coverage 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.

The scan reads SKILL.md. This mod also ships 5 executable files (scripts/count-clauses.sh, scripts/derive-tier.sh, scripts/gap-report.sh, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

runtime/capabilities/coding/skills/design-system-coverage/SKILL.md · 67 lines

How it starts

The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.

What It Does

Grades docs/instructions/design-system/ for completeness, produces a coverage inventory, and emits the tier (missing | bare | adequate | strong) the rest of the workflow uses to decide whether to stop, warn, or proceed in strict mode. Runs as Step 0 (readiness gate) and as the first skill in Step 1 — every downstream skill consumes this inventory.

Use This When

Use this as the first skill in every design-test run. The tier it emits gates the entire workflow. Never skip it; never run other design-test skills without it.

Inputs

  • Read every file under docs/instructions/design-system/ (typically tokens.md, components.md, accessibility.md, motion.md, patterns.md, responsive.md).
  • Read references/contract-clauses.md before grading.

Procedure

The decisions in steps 1–3 are deterministic — drive them with the scripts in scripts/ rather than re-deriving the logic from prose each run.

  1. Run scripts/list-contract-files.sh to enumerate which contract files exist and which are empty/stub.
  2. For each file, run scripts/count-clauses.sh <file> to count contract clauses (the file emits <path>\t<count> and skips headings, blank lines, frontmatter delimiters, and lines inside fenced code blocks). Concatenate the rows.
  3. Pipe the concatenated counts into scripts/derive-tier.sh — it emits a single tier=<missing|bare|adequate|strong> line. This is the gate decision: don't second-guess it.
  4. Emit the coverage inventory per assets/output.template.json to .paqad/design-test/runs/<run_id>/artifacts/contract-summary.json.
  5. Validate with scripts/validate-contract.sh — enforces required fields, allowed tier vocabulary, and rejects empty clause arrays when the tier is adequate or strong.
  6. If tier is missing, raise a Decision Pause Contract packet asking the user whether to invoke the documentation-update workflow inline for design-system before resuming. If tier is bare, additionally run scripts/gap-report.sh and emit each row as a DT-DS-XXXX documentation-drift finding (the script's id sequence is stable across runs so retests preserve ids).

Read the full file on GitHub · 67 lines

Files

What ships with it

8 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.

Changes

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.

  1. 9d ago First seen · 67 lines · 31 tokens per session scan A 9a3d954e3e98

Subscribe to this mod's changes

design-system-coverage is a skill published in the GitHub repository Eliyce/paqad-ai (8 stars, last pushed yesterday), licensed MIT. It adds 31 tokens to every session and 916 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.

Related

Other skills, from other repositories

double-diamond

A four-stage design method for understanding a problem, defining it clearly, exploring possible solutions, and choosing one to deliver.

Insajin/autopus-adk · 17 tokens

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.

Insajin/autopus-adk · 40 tokens

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.

Insajin/autopus-adk · 58 tokens

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.

Insajin/autopus-adk · 58 tokens

session-investigator

Investigate fast-agent session and history files to diagnose issues. Use when a session ended unexpectedly, when debugging tool loops, when correlating sub-agent traces with main sessions, or when analyzing conversation flow and timing. Covers session.json metadata, history JSON format, message structure, tool…

evalstate/fast-agent · 68 tokens

infographics

Create professional infographics using Nano Banana Pro AI with smart iterative refinement. Uses Gemini 3 Pro for quality review. Integrates research-lookup and web search for accurate data. Supports 10 infographic types, 8 industry styles, and colorblind-safe palettes.

foryourhealth111-pixel/Vibe-Skills · 55 tokens