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 motion-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/motion-review)<a href="https://agentmods.dev/skills/eliyce/paqad-ai/motion-review"><img src="https://agentmods.dev/badge/skills/eliyce/paqad-ai/motion-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/motion-review"><img src="https://agentmods.dev/badge/skills/eliyce/paqad-ai/motion-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.00017 | $0.00686 |
| Opus 5 | $0.00009 | $0.00343 |
| Sonnet 5 | $0.00003 | $0.00137 |
| Haiku 4.5 | $0.00002 | $0.00069 |
Grade A, and why
motion-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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What It Does
Audits the project's motion against motion.md: declared duration ceiling, easing curve set, reduced-motion behavior. Catches transitions that exceed the duration budget, ad-hoc easing curves not in the declared set, and components that ignore prefers-reduced-motion.
Use This When
Use for every design-test run after responsive-review.
Inputs
- Read
docs/instructions/design-system/motion.md. - Read
references/motion-checklist.md. - Read the live phase's reduced-motion screenshot results from
runtime-checks.tsif available.
Procedure
Scan and budget parsing are deterministic — drive them with the scripts.
- Run
scripts/parse-motion-budget.sh <motion.md>→ key/value rows:duration-ceiling,easing,reduced-motion. This is the declared budget. - Run
scripts/scan-animations.sh [search-root]→<file>:<line>\t<duration-ms>\t<excerpt>rows. Every duration is normalized to milliseconds (300ms,0.5s→500ms, framer-motionduration: 0.3→300ms). - Compare each emitted ms value to the declared duration ceiling. Over budget →
motionfinding, medium by default. - Run
scripts/find-reduced-motion-violations.sh [search-root]→ one row per file that animates withoutprefers-reduced-motionoruseReducedMotion(). Each row is a high severity finding (a11y blocker). - Cross-check with the live phase: did the reduced-motion walk produce identical screenshots to the static walk for animated components?
Output Contract
- Match
assets/output.template.md.contract_refismotion.md → duration/motion.md → easing/motion.md → reduced-motion. - Severity: ignored
prefers-reduced-motion→ high (accessibility), over-budget duration → medium, ad-hoc easing → low. - Output must pass
scripts/lint-findings.sh(exit 0).
Escalate / Stop Conditions
- Ask when
motion.mdis missing.
Resources
references/motion-checklist.mdscripts/parse-motion-budget.sh— declared budget frommotion.md.scripts/scan-animations.sh— every animation declaration in source, duration normalized to ms.scripts/find-reduced-motion-violations.sh— files that animate without a reduced-motion guard.scripts/lint-findings.shassets/output.template.mdagents/openai.yaml
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 · 68 lines · 17 tokens per session scan A f268e99ae61e
motion-review is a skill published in the GitHub repository Eliyce/paqad-ai (8 stars, last pushed today), licensed MIT. It adds 17 tokens to every session and 686 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…