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 richfrem/agent-plugins-skills --skill business-requirements-capturegit clone --depth 1 https://github.com/richfrem/agent-plugins-skillsWrote 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/richfrem/agent-plugins-skills/business-requirements-capture)<a href="https://agentmods.dev/skills/richfrem/agent-plugins-skills/business-requirements-capture"><img src="https://agentmods.dev/badge/skills/richfrem/agent-plugins-skills/business-requirements-capture/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/richfrem/agent-plugins-skills/business-requirements-capture"><img src="https://agentmods.dev/badge/skills/richfrem/agent-plugins-skills/business-requirements-capture.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00086 | $0.01318 |
| Opus 5 | $0.00043 | $0.00659 |
| Sonnet 5 | $0.00017 | $0.00264 |
| Haiku 4.5 | $0.00009 | $0.00132 |
Grade A, and why
business-requirements-capture 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 7d 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Business Requirements Capture
Generate structured Business Requirements Documents from exploration session captures.
Usage
python ./scripts/execute.py \
--input <file> [<file2>...] \
--mode <brd|rules|constraints> \
--output <output_file.md>
Modes:
brd(default): Full Business Requirements Document — functional/non-functional requirements, business rules, constraints, assumptions, success measures.rules: Business rules ledger only — decision logic, policy constraints, workflow conditions.constraints: Constraints and assumptions register only.
Flags:
--input PATH [PATH ...]: Session brief, problem framing, BRD draft, or prior captures--output PATH: Destination file (default:exploration/captures/brd-draft.md)--mode MODE: Output scope (default:brd)
Interactive Co-Authoring Workflow
When invoked interactively, follow this 3-stage pattern. Do not dump a full document at once.
Stage 1: Context Gathering
Ask all three questions in a single message before reading or generating anything:
- Input: Resolve input in this priority order — do not scan the filesystem before asking:
- If the user passed a problem statement or context inline — use that as primary input (mark as
[UNCONFIRMED]source) - If input files were named — read them after this question; note any that are missing
- If neither exists — halt here and ask for input before proceeding
(Check
exploration/only if no inline input and no files named.)
- If the user passed a problem statement or context inline — use that as primary input (mark as
- Output scope: Which mode fits your need?
brd— full Business Requirements Document (functional + non-functional requirements, business rules, constraints, assumptions, success measures)rules— business rules ledger only (decision logic, policy constraints, workflow conditions)constraints— constraints and assumptions register only
- Emphasis: Any specific area, stakeholder concern, or hard constraint that must be front and centre?
What ships with it
6 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.
- 7d ago First seen · 105 lines · 86 tokens per session scan A ada0d7fef2f7
business-requirements-capture is a skill published in the GitHub repository richfrem/agent-plugins-skills (6 stars, last pushed yesterday), licensed MIT. It adds 86 tokens to every session and 1,318 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
akidevsync-notes
Read and edit a project's .akidevsync/notes.json task/note file — the per-project task list written by the Aki-Dev-Sync app (github.com/lacvietanh/aki-dev-sync). Use when the user asks to list, add, pin/unpin, mark done, edit, or delete a task in that file, or mentions "task note", "note ghim", "pin task", "mark…
import
Bring a backlog in from another tracker — the mapping is shown first, and issues arrive unassigned.
cli
Raw Multica CLI — run or explain any multica … command directly, no methodology assumed.
feature
Add a feature mid-flight — grilled into a spec, ICE-scored against the backlog, slotted into a release.
fire
Offboard an agent or a person — what they own and block surfaces first, then reassignment, then the archive.
join
Take over an existing workspace — audited before anything is touched, then fixed in batches you approve.