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 ai-driven-dev/framework --skill 06-product-briefgit clone --depth 1 https://github.com/ai-driven-dev/frameworkWrote 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/ai-driven-dev/framework/06-product-brief)<a href="https://agentmods.dev/skills/ai-driven-dev/framework/06-product-brief"><img src="https://agentmods.dev/badge/skills/ai-driven-dev/framework/06-product-brief/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/ai-driven-dev/framework/06-product-brief"><img src="https://agentmods.dev/badge/skills/ai-driven-dev/framework/06-product-brief.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00042 | $0.00325 |
| Opus 5.5 | $0.00017 | $0.00130 |
| Sonnet 5.5 | $0.00008 | $0.00065 |
| Haiku 4.5 | $0.00004 | $0.00032 |
Grade A, and why
06-product-brief 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.
What it actually says
Product Brief
flowchart LR
source([idea or product]) --> frame
frame --> discover
discover -->|"ready or assumptions accepted"| shape
discover -->|"visual helps"| visualize
visualize -->|"accepted or skipped"| shape
shape -->|"evidence gap"| discover
shape --> finalize
finalize -->|"learn more"| discover
finalize -->|"change visual"| visualize
finalize -->|"revise brief"| shape
finalize -->|"authorized"| done([Product Brief])
Actions
Run the flow above. Read only the next action file.
| Action | Does |
|---|---|
| frame | establish scope and evidence path |
| discover | research, question, and challenge |
| visualize | clarify with an optional product view |
| shape | compose one Product Brief |
| finalize | refine, approve, and persist |
Transversal rules
- Keep product and lifecycle decisions with the user.
- Separate evidence, decisions, and assumptions.
- Preserve source links and existing edits.
- Ask natural questions; never expose actions, references, or unchanged state.
- Require explicit approval or caller-provided bounded authority before any write.
- Frame the opportunity; never write requirements.
What ships with it
12 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.
- actions/01-frame.md 1.1 KB
- actions/02-discover.md 1.1 KB
- actions/03-visualize.md 630 B
- actions/04-shape.md 890 B
- actions/05-finalize.md 1.6 KB
- assets/product-brief.md 1022 B
- references/brief-quality.md 441 B
- references/evidence.md 848 B
- references/handoffs.md 541 B
- references/persistence.md 492 B
- references/techniques.md 754 B
- references/visuals.md 469 B
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 · 44 lines · 42 tokens per session scan A 14c23aaf31c4
06-product-brief is a skill published in the GitHub repository ai-driven-dev/framework (523 stars, last pushed today), licensed MIT. It adds 42 tokens to every session and 325 once invoked, about $0.0002 per session on Opus 5.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-09-03.
Other skills, from other repositories
image-generation
Use this skill when the user requests to generate, create, imagine, or visualize images including characters, scenes, products, or any visual content. Supports structured prompts and reference images for guided generation.
podcast-generation
Use this skill when the user requests to generate, create, or produce podcasts from text content. Converts written content into a two-host conversational podcast audio format with natural dialogue.
skill-reviewer
Reviews DeerFlow skill packages for readiness, triggers, safety boundaries, resources, and evidence. Invoke when users ask to audit, grade, or production-check an existing skill.
knowledge-org
A guide to organising large bodies of knowledge so an AI system can navigate relationships, summaries, and layers instead of searching only flat text chunks. It covers tree indexes, knowledge graphs, file-like structures, incremental updates, and long-term memory layouts.
eval-dataset-design
A guide to creating reliable test sets for AI agents. Each evaluation task includes the request, the simulated user's behaviour, a reset starting state, and a success check that can be independently verified.
git-checkpoint
Use git as a safety net - create a checkpoint commit before risky or large changes and roll back cleanly if a change makes things worse. Use before multi-file refactors.