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 ABilenduke/copilot-developer --skill brd-plangit clone --depth 1 https://github.com/ABilenduke/copilot-developerWrote 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/abilenduke/copilot-developer/brd-plan)<a href="https://agentmods.dev/skills/abilenduke/copilot-developer/brd-plan"><img src="https://agentmods.dev/badge/skills/abilenduke/copilot-developer/brd-plan/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/abilenduke/copilot-developer/brd-plan"><img src="https://agentmods.dev/badge/skills/abilenduke/copilot-developer/brd-plan.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.00042 | $0.01319 |
| Opus 5.5 | $0.00017 | $0.00528 |
| Sonnet 5.5 | $0.00008 | $0.00264 |
| Haiku 4.5 | $0.00004 | $0.00132 |
Grade A, and why
brd-plan 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BRD Plan
Produce one proportionate business requirements document (BRD) connecting WHY → WHAT → HOW → ORDER. Investigate what can be learned, ask what requires a decision, and finish with a verifiable handoff. This skill adds structure to the host's planning workflow; it does not change Codex modes.
Ground the work
Read the user's request, prior decisions, relevant repository instructions, existing plans, and the implementation and tests that establish current behavior. Infer the actual stack and conventions from evidence. A missing repository, feature catalog, or companion skill is context, not a prerequisite. When source access is unavailable, distinguish supplied context and proposed paths from inspected facts.
Keep a compact working account of facts, user decisions, proposed defaults, and unresolved assumptions. Inspect only what can change the plan. Cite consequential repository evidence or external sources where used. Research authoritative sources when requested or when needed to resolve uncertain or changeable facts; separate sourced findings from inference.
Read question guidance when consequential gaps remain. Read the BRD outline when composing or revising a document. Consult the worked example only when an example would clarify the expected level of detail.
Resolve consequential gaps
- Identify unknowns affecting business outcomes, scope, required behavior, acceptance, constraints, or consequential implementation choices. Resolve discoverable facts with inspection first.
- Ask up to three related questions per round, using a structured question tool when available in the current mode, or concise text otherwise. Offer meaningful choices and a recommendation with its tradeoff when useful. Ask one open question when choices would be artificial.
- Incorporate the answers, investigate newly exposed uncertainty, and ask the next material question only if one remains. Do not repeat answered questions or ask the user to locate facts that tools can discover. There is no minimum question count or mandatory number of rounds.
- Use visible, reversible defaults for routine details. A consequential unresolved choice needs a user answer or evidence; elapsed time and silence do not resolve it. Preserve prior authorization and avoid adding phase-by-phase sign-offs.
What ships with it
4 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.
- 1mo ago First seen · 102 lines · 42 tokens per session scan A 5cd0d0d7a374
brd-plan is a skill published in the GitHub repository ABilenduke/copilot-developer (4 stars, last pushed 1mo ago), licensed MIT. It adds 42 tokens to every session and 1,319 once invoked, about $0.0002 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-09-16.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…