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 cenconq25/claude-code-app-studio --skill design-reviewgit clone --depth 1 https://github.com/cenconq25/claude-code-app-studioWrote 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/cenconq25/claude-code-app-studio/design-review)<a href="https://agentmods.dev/skills/cenconq25/claude-code-app-studio/design-review"><img src="https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/design-review/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/cenconq25/claude-code-app-studio/design-review"><img src="https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/design-review.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.00071 | $0.01923 |
| Opus 5.5 | $0.00028 | $0.00769 |
| Sonnet 5.5 | $0.00014 | $0.00385 |
| Haiku 4.5 | $0.00007 | $0.00192 |
Grade A, and why
design-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 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 — 254 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Review (Generic)
The general-purpose design-document validator. Use this when the artefact
is not a PRD — concept docs, design bibles, flow specs, journey maps,
narrative briefs, etc. For PRDs, route to /prd-review (this skill will
detect that case and tell you).
Read-only on the source doc. Outputs a verdict + blockers list.
Boundary vs /prd-review
| Doc type | Use |
|---|---|
design/prd/*.md |
/prd-review (specialised PRD validator) |
design/concept.md |
/design-review (concept-doc rules) |
design/design-bible.md |
/design-review (visual-system rules) |
design/flows/*.md |
/design-review (flow-spec rules) |
design/ux/*.md |
/ux-review (defer there) |
Anything else under design/ |
/design-review |
If the user invokes this skill on a design/prd/*.md path, Phase 1 detects
that and recommends /prd-review instead — does not duplicate the PRD
validator's work.
Purpose / When to Run
Run when:
- A non-PRD design doc has been authored or revised and needs a sanity pass before downstream work depends on it.
- A concept doc was just produced by
/brainstorm. - A design bible was just produced by
/design-bible. - A flow spec was extracted via
/reverse-document.
Always run in a fresh session — independent of authoring context.
Inputs
- Path to the design doc.
design/concept.mdfor cross-reference.design/registry/entities.yamlfor entity consistency..claude/docs/technical-preferences.md(constraints).- For UI-related docs:
design/design-bible.md.
Outputs
- A printed verdict: APPROVED / APPROVED WITH NOTES / NEEDS REVISION / MAJOR REVISION.
- A blockers + warnings list with section references.
- Optional
<path>.review.mdsnapshot.
Phase 1: Detect Doc Type and Dispatch
Inspect the path and the file's first 30 lines:
- If path matches
design/prd/*.mdOR file contains a## Detailed Requirementssection withTR-IDs → this is a PRD. Stop and recommend/prd-review <path>. Do not duplicate that skill's checks. - If path matches
design/ux/*.mdOR file is a UX spec → recommend/ux-review <path>. Stop. - If path is
design/concept.md→ use concept-doc rules (Phase 3a). - If path is
design/design-bible.md→ use design-bible rules (Phase 3b). - If path matches
design/flows/*.md→ use flow-spec rules (Phase 3c). - Otherwise → use generic design-doc rules (Phase 3d) and warn the user that the rule set is not specialised.
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 · 254 lines · 71 tokens per session scan A 4eff9ad1420d
design-review is a skill published in the GitHub repository cenconq25/claude-code-app-studio (42 stars, last pushed 5mo ago), licensed MIT. It adds 71 tokens to every session and 1,923 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-09-03.
Other skills, from other repositories
webgl-holographic-foil
A self-contained WebGL2 hero: thin-film interference over a crushed-foil surface whose palette shifts with the viewing angle; move the cursor to tilt the film.
html-ppt-hermes-cyber-terminal
OpenDesign + BYOK: choosing and wiring your own model, hands-on — cost, quality, and the routing decision. Built as a decision-grade AI literacy deck for engineers, IT, applied-AI teams.
html-ppt-taste-brutalist
16:9 HTML deck in tactical-telemetry / CRT-terminal taste. Deactivated-CRT charcoal slides, white-phosphor monospace, hazard-red accent, scanline overlay, ASCII syntax, density over decoration. Distilled from Leonxlnx/taste-skill brutalist-skill (Tactical Telemetry mode).
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.
glance-canonical-layouts
Use this skill to create home screen widgets using Jetpack Glance Canonical Layouts from the Android Platform Samples project, or when asked to implement standard widget layout patterns (including Check List, Image Grid, Snap Scrolling, and Standard Toolbar).
accessibility
Consolidated accessibility skill entrypoint for WCAG 2.2, ARIA Authoring Practices, cognitive accessibility, Section 508, EN 301 549, design intent verification, and the Accessibility Planner workflow.