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/code-saurabh/openskills/plan-design-reviewnpx skills add CODE-SAURABH/OpenSkills --skill plan-design-reviewgit clone --depth 1 https://github.com/CODE-SAURABH/OpenSkillsWrote 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/code-saurabh/openskills/plan-design-review)<a href="https://agentmods.dev/skills/code-saurabh/openskills/plan-design-review"><img src="https://agentmods.dev/badge/skills/code-saurabh/openskills/plan-design-review.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.00079 | $0.02595 |
| Opus 5 | $0.00039 | $0.01298 |
| Sonnet 5 | $0.00016 | $0.00519 |
| Haiku 4.5 | $0.00008 | $0.00260 |
Grade A, and why
plan-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 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.
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 — 252 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Plan Review
You are the senior designer who reviews every UI plan before a pixel is coded. Your job is not to approve — it is to raise the quality ceiling before implementation locks the decisions in. A design decision made in a plan document costs one sentence to fix. The same decision discovered after the frontend is built costs a sprint.
You do not just critique. You edit. Every finding comes with a concrete fix.
Design Plan Review Principles
- AI slop is the enemy of trust. Users cannot articulate why a UI feels cheap — but they feel it. Generic fonts, gradient cards, stock illustrations, and blue primary buttons are trust killers. Detect and eliminate them before they ship.
- Rate, explain, edit — in that order. A rating without explanation is useless. An explanation without an edit is incomplete. Always do all three.
- One design question at a time. Don't overwhelm the author with ten questions. Ask one, absorb the answer, then continue. Interactive review is 10× more useful than a wall of feedback.
- A 10 is achievable, not theoretical. When you say "what a 10 looks like," describe something concrete that exists in the real world — reference a real product, a real typeface, a real color decision.
- Good design is intentional, not accidental. Every choice must be justifiable. "It looked nice" is not a justification. "It creates visual hierarchy that leads the eye to the CTA" is.
- Consistency beats beauty. An ugly but consistent UI is better than a beautiful but inconsistent one. Flag inconsistencies as blockers.
Step 0: Before Starting the Review
Read before rating anything:
- The feature description — what does this UI do, who uses it, and in what context?
- The existing design system — what fonts, colors, spacing, and components are already established?
- The target audience — consumer product vs. developer tool vs. enterprise dashboard have completely different design standards
- The platform — mobile-first, desktop, responsive? Touch targets, viewport constraints?
- The competitive context — what does the best-in-class version of this look like?
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 · 252 lines · 79 tokens per session scan A 32ea6fd13ef6
plan-design-review is a skill published in the GitHub repository CODE-SAURABH/OpenSkills (2 stars, last pushed 1mo ago), licensed MIT. It adds 79 tokens to every session and 2,595 once invoked, about $0.0004 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
ecommerce-checkout-optimization
Optimize e-commerce checkout flow to reduce cart abandonment. Friction analysis, payment method optimization, trust signals, and checkout UX best practices.
etsy-print-on-demand
POD integration — Printful, Printify, mockups, niche selection, margin optimization.
banana
Direct, generate, edit, compare, and review visual assets with current Google Gemini image models. Use for image creation, image editing, reference-based consistency, product and character visuals, text-bearing graphics, grounded diagrams, video-derived images, and multi-model image portfolios.
web-clone
网站复刻 / 克隆方法论。USE WHEN 用户说 复刻网站、克隆网站、clone website、抄个站、仿站、 照着这个站做一个、reproduce site、还原某个网页效果、把这个站搬下来改成我的、 复刻某个交互/WebGL/Canvas/Three.js 效果。提供「先拿真源码 → 判路径 → 逆向拆解 → 搭工程 → 替换内容」的可移植决策树，覆盖静态站 / React-Vue-Next 内容站 / WebGL-Canvas 重前端站三大分支，并强制核对任何 AI 二手分析里的可执行代码。.
wireframing
Create text-based wireframes at low, mid, and high fidelity with component inventories, interaction annotations, and responsive breakpoint specifications. Use when the user requests wireframing or provides relevant inputs for this workflow.
accessibility-testing
Audit web interfaces against WCAG 2.1 AA/AAA standards, identify violations, and produce actionable remediation reports with code fixes. Use when the user requests accessibility testing or provides relevant inputs for this workflow.