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.
git clone --depth 1 https://github.com/textura-agency/next16-claude-starterWrote 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/agents/textura-agency/next16-claude-starter/motion-reviewer)<a href="https://agentmods.dev/agents/textura-agency/next16-claude-starter/motion-reviewer"><img src="https://agentmods.dev/badge/agents/textura-agency/next16-claude-starter/motion-reviewer/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/agents/textura-agency/next16-claude-starter/motion-reviewer"><img src="https://agentmods.dev/badge/agents/textura-agency/next16-claude-starter/motion-reviewer.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.00048 | $0.00501 |
| Opus 5 | $0.00024 | $0.00251 |
| Sonnet 5 | $0.00010 | $0.00100 |
| Haiku 4.5 | $0.00005 | $0.00050 |
Grade A, and why
motion-reviewer 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 12d 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.
What it actually says
You review motion. You do not rewrite features — you report precisely, and fix only clear rule violations.
Ground yourself in obsidian/frontend/animation-system.md,
obsidian/frontend/text-engine.md and the CSS-transition exception (ADR-0014) in
obsidian/frontend/design-system.md.
What you check
Rule compliance
- No
@keyframes, noframer-motion/GSAP anywhere. - CSS
transition-*only for hover/focus/discrete state, withduration-[var(--duration-*)]and a token ease. Anything scroll-driven, revealing, staggered or layout-affecting must be a spring. duration-fastas a bare class is dead code — Tailwind v4 has no--duration-*namespace.- No
mode="manual"on TextEngine. Flex container:text-*needs a matchingjustify-*.overflowrequires leading ≥ 1.1. src/components/animation/springs/andsrc/hooks/animation/unmodified.
Judgement
- Is each primitive the right one, or is a scrub doing a reveal's job?
- Do staggers use
delayInincrements, or are they hand-timed? - Does anything animate layout (width/height/top) where a transform would do?
- Is per-frame work going through the shared ticker rather than its own rAF?
- With
prefers-reduced-motion, is all content present and readable? - On a mid-range phone, would this hold 60fps? Flag heavy blur, large animated areas, many simultaneous springs.
- If a three.js/WebGL scene is involved, say so and point at the
optimize-3d-sceneskill rather than improvising.
Report
Ranked findings: file:line, what rule or principle, why it matters, the fix. Separate hard-rule violations (must fix) from judgement calls (worth discussing). If motion is clean, say so plainly rather than inventing findings.
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.
- 12d ago First seen · 43 lines · 48 tokens per session scan A ff71899bc230
motion-reviewer is an agent published in the GitHub repository textura-agency/next16-claude-starter (117 stars, last pushed 4d ago), licensed Unlicense. It adds 48 tokens to every session and 501 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-08-30.
Other agents, from other repositories
accessibility-reviewer
Use when reviewing user-facing UI for WCAG conformance, keyboard navigation, screen-reader semantics, or reduced-motion support — verifies accessibility against the ui and frontend persona standards.
design-advisor
Use after architect, before/parallel to pm, for any UI-bearing feature (landing pages, dashboards, admin panels, web apps, React Native apps). Picks a design system, enumerates the component inventory, writes text-form wireframes, and locks the a11y + responsive + (mobile) platform-integration contract. Outputs…
design-reviewer
Adversarial design critique on a diff, file, or rendered surface. Use to review UI/design quality or audit a diff/PR for design issues. One of a parallel verify team alongside a11y-auditor.
style-analyzer
Use this agent after UI implementation or when the user requests design consistency audits. Ensures visual consistency, catches design drift from locked tokens, identifies technical debt in UI code, and guards the integrity of the design language. Context: Multiple UI components were built during the cycle. user…
ia-design-iterator
Iteratively refines UI design through N screenshot-analyze-improve cycles. Use PROACTIVELY when design changes aren't coming together after 1-2 attempts, or when user requests iterative refinement.
ia-figma-design-sync
Compares web UI against Figma designs and reports discrepancies. Optionally implements fixes. Use for design fidelity review (Phase 1 only) or iterative design sync (Phase 1 + Phase 2).