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/random6913/claude-code-superkit/frontend-ui-design-criticnpx skills add RaNDoM6913/claude-code-superkit --skill frontend-ui-design-criticgit clone --depth 1 https://github.com/RaNDoM6913/claude-code-superkitWrote 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/random6913/claude-code-superkit/frontend-ui-design-critic)<a href="https://agentmods.dev/skills/random6913/claude-code-superkit/frontend-ui-design-critic"><img src="https://agentmods.dev/badge/skills/random6913/claude-code-superkit/frontend-ui-design-critic.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.00035 | $0.00952 |
| Opus 5 | $0.00017 | $0.00476 |
| Sonnet 5 | $0.00007 | $0.00190 |
| Haiku 4.5 | $0.00003 | $0.00095 |
Grade B, and why
frontend-ui-design-critic scanned grade B with 1 finding 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 4d 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.
Strips warnings and disclaimersmediumAnti-refusal
Omitting safety caveats hides risk from the user and is a common jailbreak preamble.
- Do NOT moralise. "Ugly" is not a critique. Name specific decisions that aren't working How it starts
The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend UI Design Critic
Activates on: user asks for critique / design-review / holistic-review / aesthetic-audit / "does this feel designed" · new UI surface built · 5+ UI files changed in one task.
Do NOT activate for bug fixes / single-component changes / tiny polish passes (use specialists instead).
Phase 0: Context
- Read
AGENTS.mdorCLAUDE.md+docs/architecture/frontend-*.md - Before critiquing, articulate in ONE SENTENCE what the design is going for. Examples:
- "Quiet, editorial, confident — publication with a point of view."
- "Maximalist, organic, handmade — warm independent shop."
- "Brutal, utilitarian, fast — tool for people who know what they want."
- "AI-template default — three cards with icons, purple gradient, big number hero, centered everything."
If the direction reads as "AI-template default", that IS the finding. Lead with it.
Phase 1: The Reflex Audit (scaled across whole diff)
Count the 11 defaults across the ENTIRE diff:
- Reflex fonts (Inter / DM Sans / Fraunces / Playfair / IBM Plex / Space Grotesk / Plus Jakarta Sans / Instrument / Cormorant / Newsreader / Outfit)
#000/#fffanywhere- Purple→blue gradient · cyan-on-black · neon on pure black
- Three-identical-card grid
- Big-number hero template
- Every section in a Card
- Centered-everything
- Identical padding throughout
- Rounded-icon-above-every-heading
ease-inon UI- Gray text on colored background
Scoring: 0 = solid commitment · 1–2 = some defaults · 3+ = reflex aesthetic dominates · 5+ = CRITICAL generated-looking.
Phase 2: Composition & Rhythm
- All-centered → WARNING (template reading)
- Uniform spacing
space-mdeverywhere → WARNING - Perfect equal-grid everywhere → SUGGESTION (break grid for emphasis)
- Dense-everywhere / no whitespace breathing room → SUGGESTION
- All text centered → WARNING (left-aligned reads as designed)
Phase 3: Hierarchy
- Eye doesn't land anywhere → CRITICAL (hierarchy broken)
- Typography hierarchy flat (sizes within 1.2×) → WARNING
- Competing emphasis (multiple elements fighting for attention) → WARNING
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.
- 4d ago First seen · 100 lines · 35 tokens per session scan B 301ad52e5159
frontend-ui-design-critic is a skill published in the GitHub repository RaNDoM6913/claude-code-superkit (2 stars, last pushed 1mo ago), licensed MIT. It adds 35 tokens to every session and 952 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (strips warnings and disclaimers). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
apm-review-panel
Use this skill to run a multi-persona expert advisory review on a labelled pull request in microsoft/apm. The panel fans out to five mandatory specialists plus a test-coverage specialist (active on every PR that touches src/) plus three conditional specialists (auth, doc-writer, performance-expert), all running in…
batch-bug-shepherd
Use this skill to drive a batch of suspected bugs in microsoft/apm from raw issue list to mergeable PR queue. Fan out one triage subagent per issue (LEGIT / UNCLEAR / FIXED-AT-HEAD), gate every legit bug against PRINCIPLES.md via an apm-ceo strategic-alignment pass, cross-reference legit issues against open PRs, then…
apm-issue-autopilot
Use this skill to drive any open microsoft/apm issue (bug, feature, docs, refactor, perf) from raw intake to a mergeable PR with triage as the central, paramount gate. Run the apm-triage-panel rubric per issue first, then present ONE consolidated triage review for the whole batch and escalate to the maintainer BY…
apm-spec-guardian
Use this skill to run a four-panel adversarial advisory review on any pull request that touches the OpenAPM specification artifact (docs/src/content/docs/specs/openapm-.md), its inline / sidecar JSON Schemas (docs/src/content/docs/specs/schemas/.schema.json), or the conformance fixture seed…
apm-triage-panel
Use this skill to triage one microsoft/apm issue selected by the daily sweep, the status/needs-triage fast path, or manual dispatch. Emit one synthesized comment with a decision, label set, exact milestone, and suggested next action.
cli-logging-ux
Use this skill when editing or creating CLI output, logging, warnings, error messages, progress indicators, or diagnostic summaries in the APM codebase. Activate whenever code touches console helpers (richsuccess, richwarning, richerror, richinfo, richecho), DiagnosticCollector, STATUSSYMBOLS, CommandLogger, or any…