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/shinpr/claude-code-discover/prototype-guidenpx skills add shinpr/claude-code-discover --skill prototype-guidegit clone --depth 1 https://github.com/shinpr/claude-code-discoverWhat 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.00049 | $0.00801 |
| Opus 5 | $0.00024 | $0.00400 |
| Sonnet 5 | $0.00010 | $0.00160 |
| Haiku 4.5 | $0.00005 | $0.00080 |
Grade A, and why
prototype-guide 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 2d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prototype Generation Guide
Purpose
Prototypes are hypothesis validation tools, not final implementations. They test Usability and Value risks by making ideas tangible enough for evaluation.
Output Format
Generate a single self-contained HTML file in docs/discovery/prototypes/. The file must:
- Open directly in a browser (double-click) with no build step
- Include all CSS and JavaScript inline
- Use mock data instead of real APIs
Choose the smallest browser-native implementation that makes the validation boundary observable. Use an external CSS or font resource only when a supplied design decision requires it and the prototype remains directly openable; a library choice is not part of the validation outcome.
Design Context Injection
Before generating, read the target hypothesis and the source artifacts whose decisions can change the tested flow:
- Design Principles — read
docs/product/design-principles.md - Persona — read relevant file from
docs/product/personas/ - Hypothesis Under Test — read the target hypothesis file from
docs/discovery/hypotheses/ - Vision — read
docs/product/vision.mdfor tone and value proposition
Prefer these canonical paths but accept equivalent supplied evidence. Use their content directly, represent missing decision-relevant evidence as unknown, and inspect another artifact only when it can change the tested interaction.
Blueprint Context (include when docs/product/design/ exists)
Read only artifacts from docs/product/design/ that can change the tested navigation, entities, flow, interaction, or visual direction. When present and relevant, an approved brand decision overrides ad-hoc aesthetic inference.
Additional Context (include when available)
- State Design — which states to demonstrate (Loading / Empty / Error / Partial / Success)
- Accessibility Requirements — WCAG 2.2 AA baseline
- Existing Components — use codebase-analyzer to identify reusable components if a codebase exists
- Journey Position — where in the user journey this interaction occurs
What ships with it
1 file 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.
- 2d ago First seen · 65 lines · 49 tokens per session scan A 9f4bc1d33207
prototype-guide is a skill published in the GitHub repository shinpr/claude-code-discover (10 stars, last pushed 4d ago), licensed MIT. It adds 49 tokens to every session and 801 once invoked, about $0.0002 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
blueprint-standards
Defines structural design artifact formats — information architecture, user flows, content model, brand direction, Visual Tokens, and AI interaction model. Use when creating or reviewing design artifacts that precede prototype generation.
design-perspective
Integrates design principles, WCAG 2.2 AA accessibility, persona context, and state design into product decisions. Use when reviewing UX decisions, checking accessibility, applying design principles, or ensuring state coverage in acceptance criteria.
recipe-blueprint
Selects and defines the structural design context needed by a prototype or PRD. Use when shared information architecture, flows, content, brand, Visual Tokens, or AI interaction decisions are missing.
recipe-persona
Creates or updates evidence-backed personas with the context and JTBD needed for product decisions. Use when user segments or behavior affect discovery, design, or requirements.
prototype-guide
Defines evidence-grounded prototype quality and external-generator prompt construction. Use when generating or evaluating a prototype, or exporting a prompt for Lovable, v0, or a similar tool.
recipe-refine-visuals
Use when a design-capable human wants to refine the auto-derived Visual Tokens in docs/product/design/brand-direction.md.