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.
git clone --depth 1 https://github.com/seokan-jeong/team-shinchanWrote 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/commands/seokan-jeong/team-shinchan/design-review)<a href="https://agentmods.dev/commands/seokan-jeong/team-shinchan/design-review"><img src="https://agentmods.dev/badge/commands/seokan-jeong/team-shinchan/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/commands/seokan-jeong/team-shinchan/design-review"><img src="https://agentmods.dev/badge/commands/seokan-jeong/team-shinchan/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.00025 | $0.00225 |
| Opus 5 | $0.00013 | $0.00112 |
| Sonnet 5 | $0.00005 | $0.00045 |
| Haiku 4.5 | $0.00003 | $0.00022 |
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 12d 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
Design Review Command
Compare a design source against its implementation code to detect visual mismatches in colors, layout, typography, spacing, and component structure. Supports Figma URLs (via Figma MCP API for exact values) and image files (visual analysis).
See skills/design-review/SKILL.md for full documentation.
Usage
/team-shinchan:design-review [design source] [implementation path]
Examples
/team-shinchan:design-review "https://www.figma.com/design/abc123/MyApp?node-id=1-234" "./src/components/Login.tsx"
/team-shinchan:design-review "./mockup.png" "./src/components/Login.tsx"
/team-shinchan:design-review "./designs/homepage.png" "./src/pages/Home/"
/team-shinchan:design-review "https://www.figma.com/design/abc123/MyApp"
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.
- 12d ago First seen · 25 lines · 25 tokens per session scan A 53f0b7230cd4
design-review is a command published in the GitHub repository seokan-jeong/team-shinchan (8 stars, last pushed 1mo ago), licensed MIT. It adds 25 tokens to every session and 225 once invoked, about $0.0001 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 commands, from other repositories
gbu-audit
Scope-and-rank phase only — a ranked findings list, no delegation.
audit
Audit an existing codebase. Detects stack, finds gaps, creates tasks, generates PROJECT.md.
release
Release manager for frontend and mobile. Writes App Store notes, user-facing changelog, flags stale docs and landing copy. Actions: notes | changelog | docs | sync.
discover
Run a full product discovery cycle — from outcome definition through opportunity mapping, prioritisation, and experiment design. Use when the team isn't sure what to build next, or before writing a PRD for a complex feature space.
migrate
Migrate existing PROJECT.md to the latest greatcto schema — appends missing fields without touching existing values.
close-review
Month-end close / GL compliance check — invokes accounting-reviewer to produce TM-accounting-{slug}.md with double-entry integrity, ASC 606 revenue-recognition, period-lock, and SOX ITGC gaps.