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 agentmods add skills/2233admin/design-pipeline/interface-reviewnpx skills add 2233admin/design-pipeline --skill interface-reviewgit clone --depth 1 https://github.com/2233admin/design-pipelineWrote 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/2233admin/design-pipeline/interface-review)<a href="https://agentmods.dev/skills/2233admin/design-pipeline/interface-review"><img src="https://agentmods.dev/badge/skills/2233admin/design-pipeline/interface-review.svg" alt="Measured on agentmods" 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 | $0.00138 | $0.02383 |
| Opus 5 | $0.00069 | $0.01192 |
| Sonnet 5 | $0.00028 | $0.00477 |
| Haiku 4.5 | $0.00014 | $0.00238 |
Grade A, and why
interface-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 yesterday.
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.
This is a copy
91% identical to interface-review — 11 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review the change, not just the code it left behind
A diff is not a surface. The lines a change deletes matter as much as the lines it adds, and the file it touches is rarely the whole of what it affects.
This skill owns change scope only: resolving the target, expanding changed files to affected surfaces, reading both sides of the diff, and classifying each finding. Domain rules belong to the six better-* skills. Mode, severity, consolidation, coverage, the cap, the output format, and the verdict belong to better-interface, which this skill hands the review to. Never duplicate or override their rules here.
Correctness, tests, security, and performance belong to the project's general code review. Name the concern once and move on.
Quick Reference
| Category | When to Use |
|---|---|
| Scope Resolution | Targets and commands, default branch, merge-base, PR and fork refs, repository states, nothing to review, renames, exclusions, consumer expansion |
| Removed Signals | What to look for on the - side of a hunk and which skill owns each removal |
Core Principles
1. Resolve the Change Scope First
better-interface owns mode parsing; everything after the mode is the target, so /interface-review quick pr 482 is a quick review of pull request 482. Scope Resolution holds the accepted targets and the command for each.
With no target supplied, resolve in this order and stop at the first match:
HEADis ahead ofgit merge-base origin/<default-branch> HEAD: that range plus any uncommitted changes, with the commit count and uncommitted file count stated separately.- The working tree is dirty: the uncommitted changes.
- Neither: there is no change to review. Stop and ask, per principle 2.
Order matters: checking the working tree first lets one stray formatting edit shadow a twelve-commit branch while the report still claims full coverage.
Exclude lockfiles, snapshots, generated output, vendored code, and binaries, and name what you excluded. If the scope is empty after exclusions, that is principle 2 reached by a different route: name the excluded files and ask.
What ships with it
3 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.
- yesterday First seen · 142 lines · 138 tokens per session scan A 4b8a8d1cfe00
interface-review is a skill published in the GitHub repository 2233admin/design-pipeline (7 stars, last pushed 2d ago), licensed MIT. It adds 138 tokens to every session and 2,383 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to interface-review, differing in 11 lines, and is treated as a copy.
Other skills, from other repositories
ss-motion
Apply a named StyleSeed motion to a component — either one of the 5 personality seeds (Spring/Silk/Snap/Float/Pulse × entrance/exit/hover/press/layout) or a distinctive keyword move from the motion library (toggle-flip, toggle-curtain, reveal-blur, pop-in, shimmer, …). Translates vibe words into framer-motion code…
ss-verify
The VISUAL gate — render a UI or visual artifact through its surface adapter, inspect the actual pixels, then fix and re-render until it passes the composed StyleSeed rule set.
ss-studio
Turn a product brief and optional references into three distinct creative directions, a human-selected StyleSeed interaction plan, generated image/video asset jobs, a working UI prototype, and a verified prototype-first showcase reel. Use for client concepts, app interaction exploration, trendy but coherent UI…
ss-copy
Generate UX microcopy (button labels, error messages, empty states, toasts) following a casual-but-polite voice and tone.
ss-feedback
Add appropriate user feedback states (loading, success, error, empty) to a component or page.
ss-lint
Quick automated lint — detects common design system violations in seconds.