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 Dragoon0x/dragoon-skills --skill critiquegit clone --depth 1 https://github.com/Dragoon0x/dragoon-skillsWrote 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/dragoon0x/dragoon-skills/critique)<a href="https://agentmods.dev/skills/dragoon0x/dragoon-skills/critique"><img src="https://agentmods.dev/badge/skills/dragoon0x/dragoon-skills/critique/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/dragoon0x/dragoon-skills/critique"><img src="https://agentmods.dev/badge/skills/dragoon0x/dragoon-skills/critique.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.00137 | $0.00592 |
| Opus 5 | $0.00068 | $0.00296 |
| Sonnet 5 | $0.00027 | $0.00118 |
| Haiku 4.5 | $0.00014 | $0.00059 |
Grade A, and why
critique 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 10d 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
/critique
0-100 scores for design quality. Transparent math. Every deduction is traceable to a metric in dragoon.json.
When to use
Run /critique when:
- The user asks for a design quality score, audit, rating, or grade
- Setting up a CI gate that fails when design quality drops below a threshold
- Comparing design quality before and after a redesign
- The user says "how good is this", "give me a score", "rate the design system"
What it produces
Six category scores plus an overall:
- typography - font family count, scale ratio confidence, font size variant count
- color - distinct color count, palette balance
- spacing - grid detection confidence, spacing variant count
- motion - easing variant count, duration variant count
- accessibility - alt rate, button label rate, semantic tag presence
- consistency - shadow variant count, radius variant count
Weighted overall:
typography 1.0 color 1.0 spacing 1.2 motion 0.8 accessibility 1.2 consistency 1.0
Each score includes a breakdown listing every deduction and reason. You can read exactly why your score is what it is.
Run it
node ~/.claude/skills/dragoon/skills/critique/scripts/critique.js [root]
Flags:
--manifest <p>use existing manifest instead of scanning--jsonmachine-readable--threshold <n>exit non-zero if overall score below n (CI gate)--no-breakdownshow scores only--quietshow only the final score--helpfull usage
Use as a CI gate
In package.json:
"design:check": "node ~/.claude/skills/dragoon/skills/critique/scripts/critique.js --threshold 80 --quiet"
The command exits 1 if the overall score drops below 80, blocking the PR.
What ships with it
1 file 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.
- 10d ago First seen · 58 lines · 137 tokens per session scan A 95213a7b5067
critique is a skill published in the GitHub repository Dragoon0x/dragoon-skills (4 stars, last pushed 4mo ago), licensed MIT. It adds 137 tokens to every session and 592 once invoked, about $0.0007 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-31.
Other skills, from other repositories
ss-learn
Capture a human-approved UI design lesson as a privacy-minimized local StyleSeed candidate, review it, and prepare an opt-in share package without transmitting project code, prompts, screenshots, or brand data. Use when a person asks StyleSeed to remember, learn from, generalize, review, or prepare a reusable rule…
ss-lint
Quick automated lint — detects common design system violations in seconds.
ss-review
Review UI code for design system compliance, accessibility, and best practices.
design-system-tokens
Design token management with the W3C Design Token spec, three-tier hierarchy (global/alias/component), OKLCH color, Style Dictionary transforms, and dark mode theming. Use when creating token files, implementing theme systems, or building design-to-code pipelines.
figma-extract-design-system
Extract a design system from vibe-coded production apps that never had one: inventory components, mine de-facto styling into DTCG tokens, scaffold a Storybook package, port components, and optionally round-trip tokens/components into Figma. Use when the user wants to 'extract a design system', 'create a design system…
figma-version-history
List a Figma file's version history, snapshot the file at any past version, and diff two versions (added/removed/renamed pages plus deep per-component changes). Use when the user wants to inspect Figma history — triggers: 'list Figma versions', 'what versions does this file have', 'show version history', 'snapshot…