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/benwu95/prospec/prospec-designnpx skills add benwu95/prospec --skill prospec-designgit clone --depth 1 https://github.com/benwu95/prospecWrote 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/benwu95/prospec/prospec-design)<a href="https://agentmods.dev/skills/benwu95/prospec/prospec-design"><img src="https://agentmods.dev/badge/skills/benwu95/prospec/prospec-design.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.00080 | $0.02637 |
| Opus 5 | $0.00040 | $0.01319 |
| Sonnet 5 | $0.00016 | $0.00527 |
| Haiku 4.5 | $0.00008 | $0.00264 |
Grade A, and why
prospec-design 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 today.
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 — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prospec Design Skill
Activation
When triggered, briefly describe:
- That you'll read proposal.md and determine the design workflow mode
- Generate Mode: produce design-spec.md + interaction-spec.md from proposal
- Extract Mode: reverse-extract specs from an existing design tool via MCP
- Platform adapter will guide tool-specific operations
Language Policy
Write each generated document in the language the Constitution's Language Policy rule assigns to its path — change artifacts and their archived summaries in the project's artifact language, the trust zone (Knowledge base, Feature Specs, index) in English. One skill run may write both. Keep code, identifiers, technical terms, and git commit messages in English.
CLI Prerequisite (required)
The prospec CLI is a required file for this skill — its deterministic steps call
prospeccommands. Probe BEFORE any other step; there is no manual fallback.
- Run
prospec --version(Bash). - Command not found / not executable → STOP. Ask the user to install the prospec standalone
executable — the one-click installer script from the project README (macOS/Linux
install.sh, Windowsinstall.ps1) or a release binary from GitHub Releases; prospec is NOT published to npm. Then re-run this skill. - Version older than 2.1.0 → STOP. Report the installed vs required version and ask the user to upgrade, then re-run this skill.
Hand-executing a CLI-owned mutation is NEVER the fallback — that re-introduces the nondeterministic serialization this contract exists to remove.
Startup Loading
- [STABLE] MANDATORY — Read
references/design-spec-format.mdfor design-spec.md format - [STABLE] MANDATORY — Read
references/interaction-spec-format.mdfor interaction-spec.md format - [DYNAMIC] Read
.prospec/changes/[name]/proposal.md— parse UI Scope and User Stories - [DYNAMIC] Read
.prospec.yaml— checkdesign.platformsetting (pencil|figma|penpot|html) - [DYNAMIC] Load the platform adapter reference based on
design.platform:- pencil →
references/adapter-pencil.md - figma →
references/adapter-figma.md - penpot →
references/adapter-penpot.md - html →
references/adapter-html.md - If not set → default to
htmladapter (zero-dependency fallback) - Do NOT load adapters for platforms not in use — only load the one matching
design.platform
- pencil →
What ships with it
6 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.
- today Changed 323674f9c4c6
- 4d ago First seen · 204 lines · 80 tokens per session scan A ab7d4fb64bfb
prospec-design is a skill published in the GitHub repository benwu95/prospec (5 stars, last pushed yesterday), licensed MIT. It adds 80 tokens to every session and 2,637 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
ospec-goal
Create or advance a full OSpec goal using the current document, task graph, worker, review, and evidence workflow.
ospec
Document-driven OSpec workflow for initialization, change/goal routing, validation, archiving, and durable project knowledge.
ospec-change
Create or advance a lightweight OSpec change using the classic fast workflow.
draft-design
Generate spec/DESIGN.md for the project. Asks at init whether to create a project-owned design system or reference an external one (URL/file/brand-book) as a guideline. Each project owns its DESIGN.md — no inheritance.
oma-design
AI design specialist skill with DESIGN.md management, anti-pattern enforcement, optional Stitch MCP integration, and component library guidance. Covers typography, color systems, motion design (motion/react, GSAP, Three.js), responsive-first layouts, and accessibility (WCAG 2.2).
nw-discuss
Conducts Jobs-to-be-Done analysis, UX journey design, and requirements gathering through interactive discovery. Use when starting feature analysis, defining user stories, or creating acceptance criteria.