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 tomzx/agents --skill review-mockupsgit clone --depth 1 https://github.com/tomzx/agentsWrote 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/tomzx/agents/review-mockups)<a href="https://agentmods.dev/skills/tomzx/agents/review-mockups"><img src="https://agentmods.dev/badge/skills/tomzx/agents/review-mockups/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/tomzx/agents/review-mockups"><img src="https://agentmods.dev/badge/skills/tomzx/agents/review-mockups.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.00033 | $0.01511 |
| Opus 5.5 | $0.00013 | $0.00604 |
| Sonnet 5.5 | $0.00007 | $0.00302 |
| Haiku 4.5 | $0.00003 | $0.00151 |
Grade A, and why
review-mockups 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 22d 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review Mockups
Audits UI mockups and reports findings across eight categories: coverage, usability, accessibility, consistency, state coverage, responsiveness, spec fidelity, and implementability.
A mockup set has two parts: the mockups.md narrative (screen inventory, regions, components, states, flow, responsiveness, accessibility, copy) and the per-screen HTML mockups under mockups/ that render each screen and its states.
Prerequisites
- Apply the shared SDLC conventions in
skills/sdlc/references/shared.md. - If no argument is provided, locate the feature directory under
.sdlc/features/whose frontmatterissuefield references$ISSUE_NUMBER. .sdlc/features/N-<slug>/mockups.md, or a mockups document provided in context or as a file path.sdlc/features/N-<slug>/mockups/*.html(the per-screen HTML mockups referenced frommockups.md).sdlc/features/N-<slug>/requirements.md(optional, improves coverage analysis).sdlc/features/N-<slug>/specification.md(optional, improves spec-fidelity analysis)
Steps
- Read the mockups from
.sdlc/features/N-<slug>/mockups.mdif present, otherwise from context or as a file path, then read the HTML mockups under.sdlc/features/N-<slug>/mockups/that it references. - Cross-reference against the requirements and specification if available.
- Identify issues in each of the eight categories below.
- Report findings. Omit any category that has no findings.
- Write the findings to
.sdlc/features/N-<slug>/review-mockups.mdwith frontmatterartifact: mockups,verdict(approvedif there are no blocking findings,changes-requestedif the author must address findings,rejectedfor a fundamental flaw), andreviewed_at: <ISO date>, and the findings as the body, perskills/sdlc/references/shared.md. Record any unresolved open questions in the findings body. For any question that carries meaningful risk to the implementation, also invoke/create-assumptionto record it formally.
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.
- 22d ago Changed · +8 lines c475b18c7bcf
- 23d ago Changed · -4 lines 398bc1a78ad7
- 1mo ago First seen · 143 lines · 33 tokens per session scan A de23fb2a7a48
review-mockups is a skill published in the GitHub repository tomzx/agents (13 stars, last pushed yesterday), licensed MIT. It adds 33 tokens to every session and 1,511 once invoked, about $0.0001 per session on Opus 5.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
anti-slop-design
Autonomous Principal Design Technologist. Cures vibe-coded software from AI frontend slop using curated token archetypes and 7-axis quality gating.
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
visual-ralph
Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ultragoal with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
frontend-ui-dark-ts
Build dark-themed React applications using Tailwind CSS with custom theming, glassmorphism effects, and Framer Motion animations. Use when creating dashboards, admin panels, or data-rich interfaces with a refined dark aesthetic.
open-design-setup
Prepare or repair a project's prototyping environment so open-design can build prototypes with the project's own component library and render them through the project's toolchain. Use when the library target is needed and docs/design/prototyping.md is missing, stale, or failing; excludes HTML-only design work and…
frontend-visual-qa
Audits rendered UI and specific task/object-link handoffs; excludes ordinary source citations alone. Audits already-rendered UI and Markdown/Obsidian image layout — web app, deck/slide, dashboard, design-system, or Electron/native app — via real-browser/native-app journeys and a Playwright sweep. Use after UI…