builder-product: Instructions file for Claude Code

CLAUDE.md

builder-product CLAUDE.md is an instructions file for Claude Code from RBraga01/builder-product. It costs 473 tokens per session, scanned A, original, MIT.

A repository instruction file describing how a product-development skills pack is configured, where its documents are stored, and when each skill should be used.

In plain words
What is it for?
Use it as a reference for file naming, document locations, and the order of product-planning checks.
Why use it?
It gives agents and contributors a shared process for moving from an idea to research, planning, measurement, and review.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md.

This is RBraga01/builder-product's own configuration. It tells Claude Code how to work on builder-product itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything builder-product configures →

Reuse

Borrowing it

Nothing to install: this file belongs to RBraga01/builder-product. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/RBraga01/builder-product/master/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/RBraga01/builder-product

Made for: Claude Code.

Wrote 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.

agentmods badge for builder-product CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/rbraga01/builder-product/claude-md.svg)](https://agentmods.dev/instructions/rbraga01/builder-product/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/rbraga01/builder-product/claude-md"><img src="https://agentmods.dev/badge/instructions/rbraga01/builder-product/claude-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 473 This file is loaded in full into every session.
When invoked 473 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00473 $0.00473
Opus 5 $0.00236 $0.00236
Sonnet 5 $0.00095 $0.00095
Haiku 4.5 $0.00047 $0.00047

Measured 6d ago against content hash 2662db249fd2, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

builder-product 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 6d 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.

CLAUDE.md · 48 lines

What it actually says

builder-product — Claude Configuration

Pack Version

builder-product — AI Product Skills Pack v1.0.0

File Conventions

Artifact Path
PRDs product/prd/<feature>-<date>.md
Feature scopes product/scopes/<feature>-<date>.md
Metric plans product/metrics/<feature>-<date>.md
Research synthesis product/research/<project>-synthesis-<date>.md
Experiment designs product/experiments/<feature>-design-<date>.md
AI feature validations product/ai-validation/<feature>-<date>.md
Product critiques product/reviews/<feature>/<date>-product-critique.md

Skill Trigger Sequence

For any new feature:

  1. mvp-scope-validator → before any PRD, when the idea may be over-scoped — extract hypothesis and define minimum scope
  2. prd-quality-gate → defines the problem and success metric
  3. feature-scoping → written scope before any estimate
  4. metric-definition → measurement plan with baselines before code
  5. ai-feature-validation → required if any LLM call is involved
  6. user-research-synthesis → if any research was done, synthesise before using it
  7. ab-test-design → before any experiment that informs a ship/no-ship decision

Agent Usage

Agent When to Use
product-critic After writing any PRD or feature spec, before engineering time is committed
metric-designer When designing measurement frameworks for new features
research-synthesiser After user research sessions, before decisions are made

What Makes This Pack Different From Generic Product Frameworks

Standard product frameworks produce documents. This pack produces decisions:

  • Every PRD has a measurable success metric with a baseline
  • Every estimate references a written scope
  • Every research report has an insight → decision chain
  • Every AI feature addresses hallucination UX, trust calibration, and reversibility

A completed gate means a decision was made. Not a document was written.

Changes

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.

  1. 6d ago First seen · 48 lines · 473 tokens per session scan A 2662db249fd2

Subscribe to this mod's changes

builder-product CLAUDE.md is an instructions file published in the GitHub repository RBraga01/builder-product (2 stars, last pushed 2mo ago), licensed MIT. It adds 473 tokens to every session, about $0.0024 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.

Related

Other instructions, from other repositories

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.

vercel/next.js · 7,296 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,182 tokens

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).

microsoft/vscode · 6,785 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

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.

langchain-ai/langchain · 4,469 tokens

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 tokens