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 commands/infra403/agentic-engineering-lab/product-designgit clone --depth 1 https://github.com/infra403/agentic-engineering-labWrote 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/infra403/agentic-engineering-lab/product-design)<a href="https://agentmods.dev/commands/infra403/agentic-engineering-lab/product-design"><img src="https://agentmods.dev/badge/commands/infra403/agentic-engineering-lab/product-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.00041 | $0.00593 |
| Opus 5 | $0.00020 | $0.00296 |
| Sonnet 5 | $0.00008 | $0.00119 |
| Haiku 4.5 | $0.00004 | $0.00059 |
Grade A, and why
product-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 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.
What it actually says
/product-design 命令
启动产品设计工作流，包含两个阶段：
工作流
阶段 1：需求发现（Product Discovery）
- 读取
.claude/skills/product-discovery/SKILL.md - 读取
.claude/skills/product-discovery/references/PROTOCOL.md - 创建
design-progress.json（格式见.claude/skills/product-discovery/templates/progress.md） - 加载
.claude/skills/product-discovery/knowledge/requirements-quality.md - 加载
.claude/skills/product-discovery/knowledge/theory-of-constraints.md - 激活
.claude/skills/product-discovery/roles/product-analyst.md作为 Generator - 激活
.claude/skills/product-discovery/roles/reviewer.md作为 Evaluator - 走收敛循环 GENERATE → EVALUATE → RESOLVE → CHECK
- 产出 checkpoint-1-discovery.yaml
阶段 2：领域建模（Domain Modeling）
- 上下文重置 — 仅依赖 checkpoint-1
- 读取
.claude/skills/domain-modeling/SKILL.md - 加载
.claude/skills/domain-modeling/knowledge/domain-modeling.md - 加载
.claude/skills/domain-modeling/knowledge/software-design-philosophy.md - 激活
.claude/skills/domain-modeling/roles/product-analyst.md作为 Generator - 激活
.claude/skills/domain-modeling/roles/reviewer.md作为 Evaluator - 走收敛循环
- 产出 checkpoint-2-modeling.yaml
使用方式
/product-design — 从阶段 1 开始完整流程
/product-design 需求分析 — 仅执行阶段 1
/product-design 领域建模 — 仅执行阶段 2（需已有 checkpoint-1）
产出物
design-progress.json— 全局进度状态checkpoint-1-discovery.yaml— 需求发现检查点checkpoint-2-modeling.yaml— 领域建模检查点- 结构化需求列表（FR-xxx / NFR-xxx）
- 限界上下文图 + 上下文映射 + 聚合设计
后续
完成产品设计后，使用 /architecture-design 命令继续架构设计（阶段 3-5）。
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 · 54 lines · 41 tokens per session scan A 5c5d21c2500e
product-design is a command published in the GitHub repository infra403/agentic-engineering-lab (5 stars, last pushed 4mo ago), licensed MIT. It adds 41 tokens to every session and 593 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.