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/TestAny-io/testany-agent-skillsWrote 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/testany-io/testany-agent-skills/prototype-designer)<a href="https://agentmods.dev/commands/testany-io/testany-agent-skills/prototype-designer"><img src="https://agentmods.dev/badge/commands/testany-io/testany-agent-skills/prototype-designer.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.1 | $0.00008 | $0.00405 |
| Opus 5 | $0.00004 | $0.00202 |
| Sonnet 5 | $0.00002 | $0.00081 |
| Haiku 4.5 | $0.00001 | $0.00040 |
Grade A, and why
prototype-designer 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 8d 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
Prototype Designer
在前端仓库中生成可交互的 UI 原型。基于 PRD 和 User Journey，验证交互模式和流转逻辑。
使用方式
提供 PRD 和 User Journey 文件路径：
$ARGUMENTS
为什么在 HLD 之前做原型？
文字描述的需求到前端实现之间存在巨大鸿沟。原型将交互问题提前到设计阶段暴露：
- 交互死角（Journey 中遗漏的状态和路径）
- 导航断点（页面间跳转不通顺）
- 状态遗漏（空态、错误态、边界态未考虑）
- 数据需求不明确（页面需要什么数据，为 API Contract 提供输入）
核心特点
- 100% 复用前端仓库：使用仓库已有组件库、样式方案、路由，不引入额外依赖
- 100% 遵循仓库规范：目录结构、代码风格、lint 规则全部对齐
- Mock 数据驱动：不接后端，数据结构对齐 PRD 业务实体
- 可追溯：每个页面映射到 Journey 步骤和 PRD 需求
工作流程
- 前端仓库探查：扫描技术栈、组件库、设计规范
- 原型规划：Journey→页面映射、状态矩阵、组件匹配
- 原型实现：逐页面实现 + 导航对接 + 状态覆盖
- 自检交付：可运行检查、Journey 覆盖检查、工程规范检查
请提供 PRD 和 User Journey 路径开始设计。
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.
- 8d ago First seen · 39 lines · 8 tokens per session scan A 942c2ece8a97
prototype-designer is a command published in the GitHub repository TestAny-io/testany-agent-skills (81 stars, last pushed 10d ago), licensed MIT. It adds 8 tokens to every session and 405 once invoked, about $0.0000 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-30.
Other commands, from other repositories
sddesign
Full spec-driven pipeline — walks brief → tokens → shape (spec) → craft (build) → converge → ship in one guided run. Writes .ui-craft/spec.md. Run when starting a net-new surface from scratch.
seed-create-component
A command for creating a new SEED Design component, including its source specification, recipes, React implementation, documentation, examples, and optional headless layer.
craft
One-shot build pipeline for a complete surface from an outcome recipe — inputs (or defaults) → composition → theme → build order → acceptance bar. Use when the user asks for a whole surface ("build me a dashboard", "I need a landing page") and expects a shippable result, not component-level help.
ui-flow-review
Review menus, HUD, navigation, and player flow from a UX perspective.
responsive-design-specialist
Use when a layout breaks between sizes. Arbitrary breakpoints, type that does not scale, images that blow out the grid, or a desktop design retrofitted onto mobile.
spec-screenshot
Analyze website screenshots and generate detailed implementation specs.