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 skills/darellchua2/opencode-config-template/brd-creation-skillnpx skills add darellchua2/opencode-config-template --skill brd-creation-skillgit clone --depth 1 https://github.com/darellchua2/opencode-config-templateWrote 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/darellchua2/opencode-config-template/brd-creation-skill)<a href="https://agentmods.dev/skills/darellchua2/opencode-config-template/brd-creation-skill"><img src="https://agentmods.dev/badge/skills/darellchua2/opencode-config-template/brd-creation-skill.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.00049 | $0.02972 |
| Opus 5 | $0.00024 | $0.01486 |
| Sonnet 5 | $0.00010 | $0.00594 |
| Haiku 4.5 | $0.00005 | $0.00297 |
Grade A, and why
brd-creation-skill 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.
How it starts
The opening of the file, as written. The whole thing — 346 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What I do
I provide a structured Business Requirements Document (BRD) creation workflow following the BABOK / IIBA standard — the recognized sponsor-level "why" document in the document ladder.
- BABOK BRD Template — 4-part structure (Business Requirements / Stakeholder Requirements / Solution Requirements Summary / Transition Requirements)
- docs/brd/ Naming Convention — draft files (
BRD-draft-{slug}.md) renamed to ticket-keyed files (BRD-{key}.md) after ticket creation - PLAN Back-Linkage — bidirectional traceability between BRD and PLAN files
- Discovery Interview Workflow — prompt-first flow that gathers content section-by-section with user confirmation
Position in the document ladder: the BRD is the sponsor-level document. It captures the business problem/opportunity, objectives, stakeholder needs, and a high-level solution summary — it is NOT a detailed functional spec (that is the SRS). Flow: Vision (customer-facing) → BRD (sponsor/stakeholder scope) → SRS (internal functional/technical scope). BRD is a new document type — there is no "prd" back-compat alias (prd routes to SRS).
When to use me
Use this skill when:
- A sponsor or business owner needs a business-level requirements document (the "why" and "what for", at the business/stakeholder scope)
- Someone says "create brd", "business requirements", "stakeholder requirements", "business need", "business requirements document"
- The customer-facing Vision is signed off and the business case/objectives must be formalized before detailed functional requirements (SRS)
- You need a high-level solution summary + transition requirements (training, migration, org change) — NOT detailed functional acceptance criteria
Do NOT use for: detailed functional requirements / acceptance criteria (use srs-creation-skill); customer-facing vision (use vision-creation-skill).
Trigger phrases: "create brd", "business requirements", "stakeholder requirements", "business need", "business requirements document", "write a brd"
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 · 346 lines · 49 tokens per session scan A d2f24ed1ff21
brd-creation-skill is a skill published in the GitHub repository darellchua2/opencode-config-template (6 stars, last pushed 3d ago), licensed Apache-2.0. It adds 49 tokens to every session and 2,972 once invoked, about $0.0002 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
pr-to-video
Turn a GitHub pull request (a PR URL, owner/repo#N, or 'this PR' in a checked-out repo) into a code-change explainer video — changelog, feature reveal, fix, or refactor walkthrough built from the diff, commits, and files: the input is a code change, not a website. Not a product promo (/product-launch-video) or a no-PR…
slideshow
Author a HyperFrames slideshow — a presentation, pitch deck, or interactive deck with discrete slides, fragment reveals, branching, hotspot navigation, and built-in presenter mode with speaker notes; also converts an existing page into a deck. Output is a navigable deck, not a rendered MP4. If the user didn't…
general-video
Author or edit a custom HyperFrames composition when no specialized workflow fits, or when BRIEF.md sets flow: companion. Use for longer or multi-scene pieces, brand and sizzle reels, montages, static loops, static title cards, footage remixes, and freeform builds. Use motion-graphics instead for a short unnarrated…
motion-graphics
A short, design-led motion graphic where motion is the message — kinetic typography, stat count-up, chart/data-viz hit, logo sting / brand lockup, lower-third / callout / social overlay, animated map (highlight regions, connect places, zoom to a location), animated tweet / news-article / headline, webpage / UI…
implementation-final-review
Perform the repository's risk-tiered independent final review before implementation completion. Use only when explicitly invoked or when repository instructions require it after behavior-impacting implementation work; audit the complete task diff, supported contracts, lifecycle and security boundaries, complexity, and…
hyperframes-core
The HyperFrames composition contract — build one renderable project. Use for composition structure, the data- timing attributes, class="clip", tracks, sub-compositions, variables, framework-owned media playback, deterministic-render rules, and validation. Also covers Tailwind projects and the STORYBOARD.md / SCRIPT.md…