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/rbraga01/builder-product/agents-mdgit clone --depth 1 https://github.com/RBraga01/builder-productWrote 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/rbraga01/builder-product/agents-md)<a href="https://agentmods.dev/instructions/rbraga01/builder-product/agents-md"><img src="https://agentmods.dev/badge/instructions/rbraga01/builder-product/agents-md.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.00418 | $0.00418 |
| Opus 5 | $0.00209 | $0.00209 |
| Sonnet 5 | $0.00084 | $0.00084 |
| Haiku 4.5 | $0.00042 | $0.00042 |
Grade A, and why
builder-product AGENTS.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 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
builder-product — Agent Directory
Version: v1.0.0
Three agents. Each produces a file. No file, no completion.
| Agent | Model | Output Path | Verdict Format |
|---|---|---|---|
product-critic |
Sonnet | product/reviews/<feature>/<date>-product-critique.md |
PASS / CONDITIONAL / BLOCK |
metric-designer |
Sonnet | product/metrics/<feature>-<date>.md |
Measurement plan with all baselines verified |
research-synthesiser |
Opus | product/research/<project>-synthesis-<date>.md |
Insights = Decisions count verified |
product-critic
Purpose: Audits PRDs, scopes, and feature specs against all builder-product skill gates before engineering time is committed.
Trigger: After any product document is written, before it goes to engineering.
Does not:
- Suggest creative feature directions
- PASS a vague metric on the grounds it can be refined later
- Skip Gate 5 (AI validation) for features with any LLM call
- Deliver the critique only in chat
metric-designer
Purpose: Designs north star, guardrail, and diagnostic metrics with verified baselines and a complete logging plan.
Trigger: Before writing any implementation code for a new feature.
Does not:
- Name metrics that cannot be measured with existing data without logging instrumentation in scope
- Accept "engagement" or "experience" as a metric
- Deliver the measurement plan only in chat
research-synthesiser
Purpose: Translates raw research observations into an insight → decision chain. Every insight has a corresponding decision.
Trigger: After user research sessions and before product decisions are made from that research.
Does not:
- Produce "we should think about this" decisions
- Promote 2-instance observations to patterns
- Synthesise without a defined research question
- Deliver the synthesis only in chat
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 · 47 lines · 418 tokens per session scan A a132791d4910
builder-product AGENTS.md is an instructions file published in the GitHub repository RBraga01/builder-product (2 stars, last pushed 2mo ago), licensed MIT. It adds 418 tokens to every session, about $0.0021 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
avoid-ai-writing CLAUDE.md
Instructions for conorbronsdon/avoid-ai-writing, covering claude.md, what this is, repository structure, how to make changes and architecture of the skill.
TLDR CLAUDE.md
Instructions for 0p9b/TLDR, covering claude.md — tldr maintainer guide, product, source layout, edit rules and install paths.
TLDR AGENTS.md
Instructions for 0p9b/TLDR: @./skills/tldr/SKILL.md @./skills/tldr-commit/SKILL.md @./skills/tldr-review/SKILL.md @./skills/tldr-compress/SKILL.md.
Library-First-Engineering copilot-instructions.md
Instructions for StChiotis/Library-First-Engineering: You are an AI agent operating in a Library-First Engineering (LFE) repository. This adapter is a pointer. Canonical rules live in human-readable docs.
zweig CLAUDE.md
Instructions for rornic/zweig: See AGENTS.md — the same instructions apply here.
prompt-improver AGENTS.md
Instructions for owenob1/prompt-improver: This repository packages prompt-improver as an Agent Skill.