Borrowing it
Nothing to install: this file belongs to clownware/product-dev. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/clownware/product-dev/main/CLAUDE.mdgit clone --depth 1 https://github.com/clownware/product-devWrote 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/instructions/clownware/product-dev/claude-md)<a href="https://agentmods.dev/instructions/clownware/product-dev/claude-md"><img src="https://agentmods.dev/badge/instructions/clownware/product-dev/claude-md/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/instructions/clownware/product-dev/claude-md"><img src="https://agentmods.dev/badge/instructions/clownware/product-dev/claude-md.svg" alt="Reviewed on agentmods" width="80" 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.00963 | $0.00963 |
| Opus 5.5 | $0.00385 | $0.00385 |
| Sonnet 5.5 | $0.00193 | $0.00193 |
| Haiku 4.5 | $0.00096 | $0.00096 |
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 18d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
product-dev — contributor guide
This repo builds a Claude Code plugin: an AI-assisted product development
framework that takes a vague idea to a technical spec. This file governs work
on the repo. How the plugin behaves for its users is defined inside
plugin/, which ships without this file (ADR 0011, ADR 0019).
Keep this file short and made of pointers. If something here restates a skill, a prompt, or an ADR, delete the restatement and link to the source.
Two modes
- Working on the repo (the default): editing prompts, skills, checks, ADRs,
docs. The rules below apply. Do not start the product workflow or report
.product-dev/status unless asked. - Using the plugin here (someone runs
/idea,/spec,/optimize, …): the invoked skill is the instruction set. Follow it, not this file.
Where things are defined
| Topic | Source of truth |
|---|---|
| Decisions, their status, what enforces them | ADR index, then the record itself |
| Workflow sequences, gates, checkpoints, tier escalation | each skill: product-ideation, product-flow, tech-spec, ux-optimization, status |
| Context registry, session resume, staleness, learnings, and the workflow rules all skills share (tier escalation, unclear gates, entry points) | registry-operations.md |
What runs when (run, run_when, tier, requires) |
each prompt's frontmatter under plugin/prompts/ |
| Prompt authoring, plugin development, ADR process | CONTRIBUTING.md |
| Spec package format | spec-package-schema.md |
| Checks, hooks, graduation | checks/README.md |
Rules for changes
- Find the decision first. Open the ADR index, then read the record
including its
## Amendmentsections and anything listed under "Amended by". Later text overrides earlier text. - A request that conflicts with an Accepted ADR is not a dead end. Say
which record it conflicts with, then either do the compliant version or
draft the change as an appended amendment or a new ADR with status
Proposed, and ask. Do not make the conflicting change and adjust the record to match. - ADRs are append-only. Append a dated section or write a new numbered
ADR. A new ADR that changes an older one says "amends ADR NNNN", and the
older one gets an appended note naming it. Then run
python checks/adr_index.py --write. - Never make a finding go away by editing the check, its config, or a limit. Fix the content. If the check is wrong, say so and propose the fix as its own change. Demoting a check or raising a word limit is the owner's decision and gets logged in the owning ADR.
- The plugin must stand alone. A rule about how the plugin behaves goes
in
plugin/, never only here. Anything underplugin/references bundled files through${CLAUDE_PLUGIN_ROOT}and never depends on this file, ondocs/, or on repo-root paths. - The component set is decided. Adding or removing a command, skill, or subagent needs an amendment to ADR 0004 first.
- Before pushing:
python checks/run_checks.py --ciandpython -m unittest discover -s checks/tests. Ablockfinding fails CI and stops the session from finishing; the message names the ADR and the remedy. - Hook kill-switches are the owner's. If a guard blocks you, take the move its message offers or stop and ask.
- Deferred work goes to GitHub issues, not into docs. Commits are
conventional (
type(scope): description). User-visible changes get a CHANGELOG line.
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.
- 18d ago Changed · -204 lines · -2,979 tokens per session 198c46c2264b
- 2mo 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 11d ago), licensed Apache-2.0. It adds 963 tokens to every session, about $0.0039 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-08-31.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.