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 responsive-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/responsive-review)<a href="https://agentmods.dev/skills/eliyce/paqad-ai/responsive-review"><img src="https://agentmods.dev/badge/skills/eliyce/paqad-ai/responsive-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/responsive-review"><img src="https://agentmods.dev/badge/skills/eliyce/paqad-ai/responsive-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.00027 | $0.00753 |
| Opus 5 | $0.00014 | $0.00377 |
| Sonnet 5 | $0.00005 | $0.00151 |
| Haiku 4.5 | $0.00003 | $0.00075 |
Grade A, and why
responsive-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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What It Does
Verifies the running UI at every declared breakpoint. Catches horizontal scroll, touch targets below the declared minimum, RTL parity gaps, and breakpoints declared in responsive.md that no route actually exercises.
Use This When
Use for every design-test run. Driven by the surface walk's screenshot manifest from runtime-checks.ts (Step 3).
Inputs
- Read
docs/instructions/design-system/responsive.mdfor declared breakpoints and rules. - Read the surface-walk JSON from
runtime-checks.ts. - Read
references/responsive-checklist.md.
Procedure
Enumeration and gap detection are deterministic — drive them with the scripts. The LLM picks severity and writes findings.
- Run
scripts/extract-breakpoints.sh <responsive.md>→<name>\t<width-px>TSV. This is the declared truth. - Run
scripts/find-horizontal-scroll.sh <runtime-checks.json>→ one row per(route, breakpoint)pair wherehorizontalScroll=true. Each row is a finding candidate. - Run
scripts/find-touch-target-violations.sh [--min <px>] [search-root]→ rows for icon-only / tap targets below the declared minimum (default 24px; pass--min 44for mobile-first). - If
responsive.mddeclares RTL support: cross-walk each route withdir="rtl"; flag layout breaks (no scripted detector — visual inspection of the RTL screenshot manifest). - If a declared breakpoint has zero routes exercising it in the surface walk →
documentation-driftfinding.
Output Contract
- Match
assets/output.template.md.contract_refisresponsive.md → breakpoint:<name>or a WCAG target-size id. - Severity: horizontal scroll → high, touch-target violation → high (also cross-link
WCAG-2.2-2.5.8), RTL break → medium, untested breakpoint → low. - Output must pass
scripts/lint-findings.sh(exit 0).
Escalate / Stop Conditions
- Ask when
responsive.mdis missing — defer todesign-system-coverage. - Warn when surface-walk JSON is unavailable — emit
blocked_checksand run static-only.
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 · 74 lines · 27 tokens per session scan A 40830c4c971d
responsive-review is a skill published in the GitHub repository Eliyce/paqad-ai (8 stars, last pushed today), licensed MIT. It adds 27 tokens to every session and 753 once invoked, about $0.0001 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
auto-verify
A frontend user-experience verification workflow built around Playwright, a tool for controlling browsers in automated tests. It checks important user flows and visual states in a frontend.
auto-canary
A deployment health-check skill for testing whether a recently deployed or staging website is working. It runs build, end-to-end, and browser checks, then reports a pass, warning, or failure.
testing-strategy
A testing guide that explains how to combine unit, integration, contract, and end-to-end tests. End-to-end tests check complete user flows, while integration tests check components working together.
auto-test
An end-to-end testing helper that runs the test scenarios written in a `scenarios.md` file. End-to-end tests check a complete user flow across the relevant parts of an application.
hatch3r-a11y-audit
Runs a WCAG AA accessibility audit with findings and fixes across 7 scan categories (keyboard, contrast, ARIA, reduced motion, screen reader, high contrast, automated axe). Use when auditing and remediating accessibility.
vue-component-testing
Applies the three-tier test taxonomy for Vue 3 applications: writes unit tests for composables and Pinia stores with Vitest, component tests for behaviour and user interactions with @testing-library/vue, and acceptance tests for full user flows with Playwright. Ensures tests focus on observable behaviour, not…