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 skills add jeremylongworth-source/AgentSkills --skill business-requirements-documentgit clone --depth 1 https://github.com/jeremylongworth-source/AgentSkillsWrote 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/jeremylongworth-source/agentskills/business-requirements-document)<a href="https://agentmods.dev/skills/jeremylongworth-source/agentskills/business-requirements-document"><img src="https://agentmods.dev/badge/skills/jeremylongworth-source/agentskills/business-requirements-document/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/jeremylongworth-source/agentskills/business-requirements-document"><img src="https://agentmods.dev/badge/skills/jeremylongworth-source/agentskills/business-requirements-document.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.00092 | $0.00650 |
| Opus 5 | $0.00046 | $0.00325 |
| Sonnet 5 | $0.00018 | $0.00130 |
| Haiku 4.5 | $0.00009 | $0.00065 |
Grade A, and why
business-requirements-document 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 10d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Business Requirements Document
Core Workflow
- Identify the business problem, decision context, sponsor, stakeholders, affected teams, customers, systems, process boundaries, and target outcome.
- Separate business objectives, stakeholder needs, business requirements, solution requirements, assumptions, constraints, risks, and open questions.
- Capture current state, future state, process impacts, business rules, data needs, reporting needs, compliance concerns, and operational handoffs.
- Define measurable success criteria and acceptance signals before discussing implementation options.
- Create traceability from objective to requirement to acceptance criteria, owner, evidence source, priority, and validation method.
- Flag conflicting requirements, missing decision owners, weak evidence, unresolved dependencies, and approval gates before handoff.
BRD Principles
- Keep the BRD business-facing. Describe what the business needs and why before proposing how a product, system, vendor, or team should implement it.
- Use clear requirement language: must, should, may, will not.
- Prefer numbered requirements when traceability, signoff, testing, or vendor comparison matters.
- Separate in-scope, out-of-scope, and future-consideration items.
- State assumptions as assumptions, not decisions or evidence.
- Convert vague goals into observable business outcomes, metrics, or review criteria.
- Include human approval points when requirements affect budget, contracts, staffing, customer commitments, compliance, billing, privacy, or operations.
Safety Rules
- Do not invent stakeholder approval, budget authority, legal obligations, compliance status, vendor commitments, or production readiness.
- Do not turn business requirements into technical architecture unless the user asks for a solution design or implementation plan.
- Escalate when requirements conflict with policy, legal/compliance, privacy, accessibility, security, finance, or contractual commitments.
- Mark missing source material and unresolved decisions explicitly.
What ships with it
3 files 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.
- 10d ago First seen · 70 lines · 92 tokens per session scan A 86b2a31ced4a
business-requirements-document is a skill published in the GitHub repository jeremylongworth-source/AgentSkills (1 stars, last pushed 8d ago), licensed MIT. It adds 92 tokens to every session and 650 once invoked, about $0.0005 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 skills, from other repositories
issue-authoring
Draft or refine IDD-ready GitHub issues, roadmap issues, and sub-issues before the normal IDD execution loop begins. Use when a request is too large or ambiguous for one reviewable change, when work needs decomposition or dependency encoding, or when the user asks for issue drafting, roadmap planning, or…
idd-spec-audit
Semantic audit of the IDD instruction corpus for leaked session context, cross-file contradictions, fresh-memory completability gaps, automation blockers, and restatement-discipline drift. Use on request to audit .github/instructions, the issue-authoring skill bundle, and the installed agent entry files (CLAUDE.md…
unity-yaml-format
Inspect, explain, diff, and carefully edit Unity text-serialized files such as .unity, .prefab, .asset, and related YAML-based project files. Use when mapping class IDs and fileIDs, tracing object references, reviewing merge conflicts, or making minimal safe edits to existing UnityYAML documents.
joedevflow
Development workflow. Use when building a feature, creating an MVP, refactoring code, fixing a bug, or any task that involves writing or changing implementation code.
authos-web-integration
Integrate AuthOS into browser, React, Vue, or plain TypeScript applications using @drmhse/sso-sdk and the AuthOS React/Vue adapters. Use when adding OAuth redirects, password login, magic links, passkeys, MFA callback handling, token refresh, or frontend session state.
authos-backend-integration
Secure backend APIs with AuthOS-issued JWTs and the AuthOS Node server adapter. Use when building an API that must verify AuthOS bearer tokens, enforce JWT claims, add Express middleware, validate JWKS keys, or create a backend-owned session after a browser OAuth callback.