Borrowing it
Nothing to install: this file belongs to friedbotstudio/baseline. 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/friedbotstudio/baseline/main/.claude/skills/brd/SKILL.mdgit clone --depth 1 https://github.com/friedbotstudio/baselineWrote 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/friedbotstudio/baseline/brd)<a href="https://agentmods.dev/skills/friedbotstudio/baseline/brd"><img src="https://agentmods.dev/badge/skills/friedbotstudio/baseline/brd/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/friedbotstudio/baseline/brd"><img src="https://agentmods.dev/badge/skills/friedbotstudio/baseline/brd.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.00064 | $0.00729 |
| Opus 5.5 | $0.00026 | $0.00292 |
| Sonnet 5.5 | $0.00013 | $0.00146 |
| Haiku 4.5 | $0.00006 | $0.00073 |
Grade A, and why
brd 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.
How it starts
The opening of the file, as written. The whole thing — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BRD — Business Requirements Document
You are drafting a BRD. BRDs are heavier than intakes — they exist when a request needs explicit sign-off from named business stakeholders, and when the why and the what must survive independently of the how (the spec).
Use a BRD when:
- Multiple teams or external stakeholders need to align.
- Regulatory, legal, or compliance concerns shape the requirements.
- Business milestones or contractual dates are tied to the work.
- Budget or headcount implications warrant an approved scope.
Don't use a BRD for: single-team feature work, quickfixes, or internal refactors. Those need an intake + spec, nothing more.
Prerequisite
Either /intake has completed (there's a corresponding docs/intake/<slug>.md), OR the user is starting directly at BRD because the intake exists upstream (e.g., in Linear/Jira) and they want to formalize it here.
Inputs
- The intake document (if any) — it supplies Problem and Goal.
- The user's additional context about stakeholders, timelines, and compliance.
template.mdin this skill directory.
Steps
- If a corresponding intake exists at
docs/intake/<slug>.md, read it. Map Problem → Business objective and Goal → Executive summary. - Read
template.md. Every heading must appear in the output. - For each section, write content that answers the questions in the template comments. If unknown, list the gap under Open questions — never fabricate stakeholder names, dates, or dollar amounts.
- Name every requirement with an ID:
BR-001,BR-002, … for business reqs;FR-001, … for functional;NFR-001, … for non-functional. Downstream spec AC will reference these IDs. - Write to
docs/brd/<slug>.md(same slug as the intake, if one exists). - Tell the user: "BRD drafted at
docs/brd/<slug>.md. Sign-offs required from: . Open questions: N. Next:/scout(or get sign-offs first if you want to freeze scope)."
Drafting rules
- Requirements are testable, not aspirational. "The system shall support peak traffic" is aspirational. "The system shall sustain 500 RPS with P95 < 200ms" is testable.
- Separate business from functional from non-functional. A mixed list becomes unactionable.
- Risks must have owners. "Risk: the vendor API could change" with no owner is noise. Either name who monitors it or delete it.
- Sign-offs are names, not titles. "Head of Compliance" can't sign — their replacement, who is a specific person, can.
- Do not write the solution. The BRD says what must be true; the spec says how. If you catch yourself writing "we'll use Kafka", stop — that belongs in
/spec.
What ships with it
1 file 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.
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 · 46 lines · 64 tokens per session scan A 5b2ab80180f7
brd is a skill published in the GitHub repository friedbotstudio/baseline (14 stars, last pushed 13d ago), licensed Apache-2.0. It adds 64 tokens to every session and 729 once invoked, about $0.0003 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-30.
Other skills, from other repositories
code-review-with-lsp
Code review with LSP-powered code intelligence. Uses MCP tools (diagnostics, hover, references, definition, symbols) for semantic code understanding, not just text grep.
i18n-check
An internationalization (i18n) check for software that supports multiple languages. It compares translation files with the text and translation keys used by the code.
vue-best-practices
A review checklist for Vue 2 and Vue 3 components, covering component names, prop declarations, TypeScript casts, API styles and complex template expressions.
gdpr-audit
GDPR compliance audit of code, plans, schemas, or IaC. Produces a findings report with article citations, severity, confidence, and fixes; flags evidence gaps. Not a substitute for a DPO/lawyer.
cognitive-walkthrough
Deep-dive usability evaluation of specific user tasks. Simulates novice user cognition step-by-step to identify learnability issues, unclear actions, and points of confusion.
owasp-ai-testing
AI trustworthiness testing using OWASP AI Testing Guide v1. Execute 32 test cases across 4 layers (Application, Model, Infrastructure, Data) with practical payloads and remediation.