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 educlopez/ui-craft --skill finalizegit clone --depth 1 https://github.com/educlopez/ui-craftWrote 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/educlopez/ui-craft/finalize)<a href="https://agentmods.dev/skills/educlopez/ui-craft/finalize"><img src="https://agentmods.dev/badge/skills/educlopez/ui-craft/finalize/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/educlopez/ui-craft/finalize"><img src="https://agentmods.dev/badge/skills/educlopez/ui-craft/finalize.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 25 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00085 | $0.01830 |
| Opus 5.5 | $0.00034 | $0.00732 |
| Sonnet 5.5 | $0.00017 | $0.00366 |
| Haiku 4.5 | $0.00009 | $0.00183 |
Grade A, and why
finalize 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 1mo 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context: this sub-skill is one lens of the broader ui-craft skill. If the ui-craft skill is also installed, read its SKILL.md first for Discovery + Anti-Slop + Craft Test, then apply the specific lens below.
Load the ui-craft skill. This command produces findings only — do NOT edit code.
Step 1 — Brief check (gate)
Look for .ui-craft/brief.md.
- Absent: STOP. Output: "No brief found. Run
/brieffirst./finalizerequires a design brief to distinguish intentional decisions from findings." Do not proceed. - Present: load it. Extract principles (numbered, in conflict-resolution order). These are the override registry for Steps 4–5.
Step 2 — Detector
Run npx ui-craft-detect on $ARGUMENTS (or current working surface if no argument).
Capture all output. Every Critical detector finding maps directly to a block-ship finding in the report. Preserve detector source labels.
Step 3 — Token check
Quick three-question audit (no deep read required):
- Are all three token layers present (primitives → semantic → component)?
- Are both light and dark modes explicitly authored (not inverted)?
- Are all seven token categories represented (color, spacing, radius, shadow, typography, motion, z-index)?
Any "no": flag as Major. Do not block ship. Append a recommendation: "Run /tokens to close the gap at [category]."
Step 3b — Craft-intent check (full surfaces only)
Applies only when the target is a complete surface (dashboard, landing, auth, settings shell, portfolio) — skip for single components.
- Signature bet present? Scan for exactly one memorable decision from
references/craft-intent.md§3 (product / auth / marketing lists). Zero → Major ("no signature — surface is competent but anonymous; run/bolderor/polish"). Two or more competing → Major ("signature bets stack — keep the strongest, cut the rest"). - Variance matches surface? Layout risk visibly inconsistent with the surface's DESIGN_VARIANCE default (e.g. experimental asymmetry on an auth form, or a landing that is one centered symmetric column) → Major, unless the brief or spec records the deviation.
- Craft Read recorded? If a
.ui-craft/spec.mdsection or session declared a Craft Read, verify the built surface matches it (theme, variance, signature). Mismatch → Major with the specific delta.
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.
- 1mo ago First seen · 149 lines · 85 tokens per session scan A 6b7ab59c5433
finalize is a skill published in the GitHub repository educlopez/ui-craft (388 stars, last pushed 3d ago), licensed MIT. It adds 85 tokens to every session and 1,830 once invoked, about $0.0003 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-08-30.
Other skills, from other repositories
check
Reviews diffs, PRs, release readiness, and publishing follow-through. Use when asked to review, triage issues or PRs, or ship. Not for debugging root causes or prose.
write
Rewrites and polishes Chinese or English prose, technical instructions, and product copy. Use when drafting, editing, localizing, or cutting AI tone. Not for code comments or commit messages.
software-in-worten
Übersetzt zwischen Benutzeroberfläche und Text — in beide Richtungen. Aus einer beschriebenen Oberfläche wird ein Skill; aus einem Skill wird eine Oberfläche. Nutzen, wenn eine Anwendung entworfen wird und der Ablauf noch unklar ist, wenn ein bestehendes Werkzeug als Skill verfügbar gemacht werden soll, wenn…
huashu-agent-swarm
Multi-agent swarm parallel collaboration using pure git self-organisation, ideal for large-scale project development. Use when the user mentions "swarm mode", "multi-agent", "parallel development", or "agent swarm".
anti-ui-slop
Stop coding agents from shipping generic UI. Extend the product's design system, use UIZZE evidence only when useful, cover required states, and inspect the rendered result.
popular-web-designs
54 real design systems (Stripe, Linear, Vercel) as HTML/CSS.