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 zxpmail/ReqForge --skill design-makergit clone --depth 1 https://github.com/zxpmail/ReqForgeWrote 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/zxpmail/reqforge/design-maker)<a href="https://agentmods.dev/skills/zxpmail/reqforge/design-maker"><img src="https://agentmods.dev/badge/skills/zxpmail/reqforge/design-maker/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/zxpmail/reqforge/design-maker"><img src="https://agentmods.dev/badge/skills/zxpmail/reqforge/design-maker.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 13 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Prompt Injection · line 1 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
- high Prompt Injection · line 76 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
- high Prompt Injection · line 76 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
- high Prompt Injection · line 100 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
- high Prompt Injection · line 106 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
- high Prompt Injection · line 118 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
- high Prompt Injection · line 135 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
- high Prompt Injection · line 147 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
- high Prompt Injection · line 156 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
- high Prompt Injection · line 230 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
- high Prompt Injection · line 321 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
- medium Excessive Agency · line 26 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium MCP Rug Pull · line 369 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00000 | $0.04966 |
| Opus 5.5 | $0.00000 | $0.01986 |
| Sonnet 5.5 | $0.00000 | $0.00993 |
| Haiku 4.5 | $0.00000 | $0.00497 |
Grade A, and why
design-maker 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 — 390 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: design-maker description: Used when the Design Brief is complete and the user needs to generate mockups. Reads Product-Spec.md and Design-Brief.md, then generates a complete set of design deliverables through a design tool MCP, including all pages, state variants, component specifications, design tokens, UI-Spec.md, and DESIGN.md (Google design.md format). version: 1.1.0 updated: 2026-06-27 requires: []
[Task] Read Product-Spec.md and Design-Brief.md, then generate complete design deliverables through a design tool MCP. Ensure that every feature with UI in the Product Spec has a corresponding design page, and every page covers all critical state variants.
**Typical entry**: User just finished `/design-brief-builder` and chose option A (or said「继续/默认」) in Next Step Gate — treat that as explicit invocation.
[Not For] - Defining visual direction or style preferences -> use /design-brief-builder instead - Writing code from designs -> use /dev-builder instead - Projects without a design tool MCP available -> skip this skill and go straight to /dev-builder
[Dependency Check] Automatically executed as the first step when the Skill starts.
Required:
- Product-Spec.md → If missing, prompt the user to call /product-spec-builder first
- Design-Brief.md → If missing, prompt the user to call /design-brief-builder first
- Design tool MCP → See the design tool detection process below
Optional:
- references/design-self-critique.md → used in verification if available
Design tool detection process:
1. Ask the user whether they want to use Pencil or Figma
2. Check if the corresponding MCP is connected
3. Connected → Continue
4. Not connected → Attempt to connect the MCP, or prompt the user to connect
5. User does not have the corresponding design software installed → Prompt the user to install it and retry
6. User chooses to skip → Exit design-maker; subsequent workflow continues in no-mockup mode
[First Principles] Full Coverage Principle: Every feature with UI in the Product Spec must have a design page. Miss one page and development loses one reference — the consequence is development by guessing. State Completeness Principle: Every page must have more than just a default state. Empty state, loading state, error state, active state — pages with interactivity must cover critical state variants. Components First Principle: Build reusable components first, then compose pages from them. Avoid drawing the same button 10 times across 10 pages, requiring 10 changes for a single update. Document-Driven Principle: All design decisions come from Product-Spec.md and Design-Brief.md. Do not improvise based on personal preference, and do not add features not described in the documents.
[Output Style] Tone: Designer presenting mockups to an engineering team — structured, precise, complete. Every page and variant is explicitly listed. Principles: - V Every feature with UI in the Spec has a design page - V Every interactive page covers empty, loading, error, and active states - V Design tokens are documented (not "looks about right") - X No improvised features — everything comes from Product-Spec.md and Design-Brief.md
[Design Coverage Checklist] Before delivering, verify each dimension:
| Dimension | Must-Have | Recommended |
|-----------|-----------|-------------|
| **Page Coverage** | Every Spec UI feature has a design page | State variants (empty/loading/error) for interactive pages |
| **Component System** | Reusable components extracted before page composition | Design tokens for colors, typography, spacing, radius |
| **Spec Fidelity** | Layout and content match Product-Spec.md item by item | Visual direction matches Design-Brief.md mood and notes |
| **Self-Critique** | references/design-self-critique.md executed (all >=3) | Anti-ai-slop checklist from design-brief-builder reviewed |
| **Consistency** | Same component looks same across pages | Design tokens referenced correctly, no ad-hoc values |
What ships with it
8 files 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.
- 1mo ago First seen · 390 lines · 0 tokens per session scan A 54dd9206baaa
design-maker is a skill published in the GitHub repository zxpmail/ReqForge (18 stars, last pushed 10d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,966 tokens. 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-30.
Other skills, from other repositories
ui-mockup
Create UI mockups at three fidelity levels — ASCII wireframes for quick iteration, standalone HTML mockups for delivery with requirements, and live prototypes for interaction testing.
oma-design
Define or review a visual system, DESIGN.md, or redesign direction. Use for typography, layout, color, motion, and interaction design decisions.
ijfw-ui-spec
Use when the user says: 'ui spec', 'design contract', 'ui audit setup', 'lock the design', 'visual contract', 'ui review setup', or '/ijfw-ui-spec'. Produces UI-SPEC.md as the visual design contract before any frontend or visual-artifact build, and dispatches ijfw-ui-auditor as the final 6-pillar gate.
ijfw-design
Use when the user says: 'design', 'redesign', 'UI', 'UX', 'dashboard', 'page', 'component', 'make it look better', 'polish', 'pretty', 'professional', 'user experience', 'layout', 'visual', 'accessibility', 'colors', 'typography', 'brand'.
design
Design and critique any visible UI, before and after building. Trigger on UI work: "improve the UI", "redesign", "polish", "make it look better", "visual upgrade", "design review", "design audit", "layout fix", "UX improvement", or any task whose deliverable is a page, screen, or component that renders. Shapes a…
design-bootstrap
Bootstrap a design system from a Figma file via MCP: extract token variables, identify components, scaffold foundation docs and a component inventory. Use when starting a new project with a Figma file. Do not use when docs exist or there is no Figma file.