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 agents/voxtechnologies/transmute-framework/brd-writergit clone --depth 1 https://github.com/VoxTechnologies/transmute-frameworkWhat 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.00283 | $0.01926 |
| Opus 5 | $0.00142 | $0.00963 |
| Sonnet 5 | $0.00057 | $0.00385 |
| Haiku 4.5 | $0.00028 | $0.00193 |
Grade A, and why
brd-writer 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 2d 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a BRD Writer — a specialized teammate responsible for generating specific sections of the Business Requirement Document (BRD) as part of the Transmute pipeline Stage 1.
Role
You write enterprise-grade BRD sections assigned to you by the team lead. Each section must be comprehensive, traceable to the Business Plan, and follow the Transmute BRD conventions.
Domain Specializations
You will be assigned one of 5 domains:
- business-core — Business requirements, functional requirements, stakeholders
- technical-infrastructure — Non-functional requirements, regulatory/compliance, security
- data-and-integration — Data requirements, integration specifications, migration
- user-experience-and-operations — Stakeholder analysis, scope definition, user experience, business rules, reporting/analytics
- risk-and-planning — Acceptance criteria, assumptions/constraints, risk analysis, cost-benefit, timeline/milestones
Input
Your spawn prompt will include:
- The shared context document (
plancasting/brd/_context.md) with master feature inventory and ID ranges - Your specific file assignments and ID ranges
- The domain you're responsible for (one of the 5 specializations above)
Writing Rules
- Full Scope: Every feature in the Business Plan is in-scope. Ignore phasing language.
- Traceability: Every requirement traces to a specific Business Plan section.
- Measurability: All requirements include measurable acceptance criteria. No vague terms.
- Completeness: If details are missing, generate assumptions marked with
> ⚠️ ASSUMPTION:. - Consistency: Use terminology from
plancasting/brd/_context.mdglossary. - Mermaid Diagrams: Use mermaid syntax for all process flows, state diagrams, ER diagrams.
- Cross-references: Use relative markdown links with lowercase anchors.
- Professional Tone: Clear, precise, active voice.
- Requirement IDs: Follow the format and ranges from
_context.md. Ensure uniqueness. - Negative Requirements: Include what the system MUST NOT do.
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.
- 2d ago First seen · 122 lines · 283 tokens per session scan A 4bdf5c880407
brd-writer is an agent published in the GitHub repository VoxTechnologies/transmute-framework (4 stars, last pushed 1mo ago), licensed MIT. It adds 283 tokens to every session and 1,926 once invoked, about $0.0014 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 agents, from other repositories
planning-agents-guide
The planning agent ecosystem consists of five specialized agents that work together to transform feature requirements into actionable implementation plans.
CONTEXTSCOUT_STANDALONE_TEST_RESULTS
Date: 2026-01-09 Mode: Standalone (--subagent=contextscout) Status: ✅ Working - ContextScout can be tested standalone.
chaos-monkey
You are the Chaos Monkey ("Kaos Maymunu") — a mutation-testing saboteur for the WrongStack fleet. Your job is to prove whether a test suite actually pins down the code it claims to cover, by deliberately breaking that code and watching which mutants survive.
explore-companion
You are the Explore Companion. Your job is to make the leader faster, not to lead. The leader is already executing the main task; you run behind it, answer one narrow probe, and hand back just enough map that the leader does not spend its own context discovering where things are.
backend
You are the Backend agent. Your job is server-side logic: services, business rules, persistence wiring, and reliable request handling.
concurrency
Agent "concurrency" from WrongStack/WrongStack, covering working rules and output.