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 instructions/clownware/product-dev/claude-mdgit clone --depth 1 https://github.com/clownware/product-devWhat 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.03942 | $0.03942 |
| Opus 5 | $0.01971 | $0.01971 |
| Sonnet 5 | $0.00788 | $0.00788 |
| Haiku 4.5 | $0.00394 | $0.00394 |
Grade A, and why
product-dev CLAUDE.md 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 — 268 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Development Framework
AI-assisted product development from vague idea to technical spec. Guides users through structured UX research, hypothesis formation, and prototype planning.
Repo Structure
The framework prompts are bundled inside the plugin at plugin/prompts/ so the
plugin is self-contained and distributable. Skills, commands, and the subagent
reference them via ${CLAUDE_PLUGIN_ROOT}/prompts/... (ADR 0011).
plugin/prompts/
├── 01_ux_research/
│ ├── 00_fuzzy_front_end/ # Phase 00: Idea capture + exploration
│ ├── 01_define_problem/ # Phase 01: Problem statement + persona
│ ├── 02_objectives/ # Phase 02: Core objective + metrics
│ ├── 03_solution_hypothesis/# Phase 03: Solution concept + hypothesis
│ ├── 04_user_flow/ # Phase 04: User flow + screens
│ ├── 05_prototype/ # Phase 05: Prototype scoping + test design
│ └── 06_post_test_synthesis/# Phase 06: Test analysis + evaluation
├── 02_tech_requirements/ # Tech spec: data models, APIs, business rules, NFRs
├── 07_ux_optimization/ # Reverse pass: extract artifacts from an existing product (ADR 0013)
├── 03_tool_selection_setup/ # Environment and tooling (Tier 3, not in active workflow)
├── 04_bridge_to_architecture/ # Architecture transition prompts (Tier 3)
└── 05_implementation_docs/ # Implementation planning (Tier 3)
Non-framework reference material (build guides, IDE rules, portfolio prompts)
remains at repo root under prompts/dev/ and is not part of the plugin bundle.
Frontmatter schema (each prompt file):
name: kebab-case-name
run: always | entry_point | context_gated
run_when: [plain-English condition, only for context_gated]
produces: artifact_name
requires: [dependency_artifact_1, dependency_artifact_2]
tier: 1 | 2
Prompt body structure: <system_context> sets your role, instructions define the output, <constraints> set boundaries, <example> shows quality. Template variables use {{artifact_name}} syntax. See ADR 0001 for full schema.
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 · 268 lines · 3,942 tokens per session scan A 2628db87ffe4
product-dev CLAUDE.md is an instructions file published in the GitHub repository clownware/product-dev (3 stars, last pushed 6d ago), licensed Apache-2.0. It adds 3,942 tokens to every session, about $0.0197 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 instructions, from other repositories
oh-my-posh AGENTS.md
Instructions for JanDeDobbeleer/oh-my-posh, covering agent instructions, project overview, tech stack, key commands and go - run from src/.
tamagui AGENTS.md
AGENTS.md instructions for tamagui/tamagui, covering tamagui — agent operating contract, finish what you start, then merge it back, tamagui testing guide, running tests and kitchen sink tests.
ui AGENTS.md
AGENTS.md instructions for nuxt/ui, covering agents.md, project overview, project structure, commands and cli for scaffolding.
oh-my-posh powershell.instructions.md
Instructions for JanDeDobbeleer/oh-my-posh: Refer to skills/powershell/SKILL.md for the full PowerShell coding standards.
ui-components AGENTS.md
Instructions for starc007/ui-components, covering beui v2 — agent guide, commands, layout, component catalog and components (motion category — primitives).
webgradients AGENTS.md
Instructions for itmeo/webgradients, covering agents.md, files and what they're for, why gradients.json only had 11 entries until now, webgradients.css structure and gradients-parsed.json / gradients.json structure.