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/voxtechnologies/transmute-framework/brdnpx skills add VoxTechnologies/transmute-framework --skill brdgit 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.00079 | $0.03457 |
| Opus 5 | $0.00039 | $0.01729 |
| Sonnet 5 | $0.00016 | $0.00691 |
| Haiku 4.5 | $0.00008 | $0.00346 |
Grade A, and why
brd 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 — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Transmute — BRD Generation (Stage 1)
Read the detailed guide at ${CLAUDE_SKILL_ROOT}/references/brd-detailed-guide.md for the complete agent team architecture, teammate spawn prompts, token budget management, review agent checklists, remediation procedures, and writing guidelines.
Prerequisites
Before starting, verify:
./plancasting/businessplan/directory exists and contains.mdor.pdffiles. If missing or empty, STOP: "Stage 1 requires a Business Plan at./plancasting/businessplan/. Place your business plan files (.md or .pdf) there before running Stage 1."./plancasting/tech-stack.mdexists (created by Stage 0). If missing, STOP: "Stage 1 requiresplancasting/tech-stack.mdfrom Stage 0. Run Stage 0 first."
Critical Framing
This BRD uses the Full-Build Approach: ALL features described in the Business Plan are built as a single, complete product. No MVP, no phased rollout, no feature deferral. If the Business Plan describes "Phase 1, Phase 2, Phase 3" — IGNORE the phasing. Features labeled "future", "planned", "roadmap", or "long-term" are INCLUDED in full scope. Only features explicitly marked "out-of-scope" are excluded.
Execution Flow
Step 1: Read and Analyze Inputs
Read and fully internalize:
- All files in
./plancasting/businessplan/(supported formats:.mdand.pdf) ./plancasting/tech-stack.md
Check Session Language in ./plancasting/tech-stack.md. Generate ALL BRD documents in the specified language. Technical identifiers (requirement IDs like FR-001, section headers, cross-reference codes) remain in English.
Language Inheritance: Subsequent stages (PRD, audits, reports) will read the Session Language section from plancasting/tech-stack.md — NOT from BRD documents. The BRD's language serves as a reference, but the canonical language setting is always in tech-stack.md.
Adapt BRD structure based on product type in plancasting/tech-stack.md:
- Web applications: Standard structure
- Mobile applications: Add platform-specific requirement categories (App Store/Play Store guidelines, device permissions, offline capabilities)
- IoT / Embedded: Add hardware requirement categories (environmental requirements, power requirements, connectivity protocols, certification requirements)
- Desktop applications: Add platform-specific requirements (Windows/macOS/Linux compatibility, installation/update mechanisms, system resource requirements)
- AI/ML products: Add model requirement categories (training data requirements, inference latency, accuracy metrics, bias/fairness requirements)
What ships with it
1 file 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.
- 2d ago First seen · 205 lines · 79 tokens per session scan A 79e070805519
brd is a skill published in the GitHub repository VoxTechnologies/transmute-framework (4 stars, last pushed 1mo ago), licensed MIT. It adds 79 tokens to every session and 3,457 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-08-31.
Other skills, from other repositories
knowledge-base
Create and maintain a Markdown knowledge base that any AI agent can read, search, and update. Use when the user wants to start a knowledge base, add or update notes, organize docs/notes for an agent or LLM to consume, build an index of notes, or run a cleanup/maintenance pass on an existing MD knowledge base. Triggers…
code-review
Use when code has been written and needs validation before committing, or when the user asks for a code review or security check.
test-generation
Use when the user asks for tests, mentions TDD, or when new code has been written and needs test coverage.
scientific-schematics
Create publication-quality scientific diagrams using Nano Banana 2 AI with smart iterative refinement. Uses Gemini 3.1 Pro Preview for quality review. Only regenerates if quality is below threshold for your document type. Specialized in neural network architectures, system diagrams, flowcharts, biological pathways…
statistical-power
Sample-size and statistical power calculations for planning studies. Use whenever someone asks "how many subjects/samples/replicates do I need", wants an a priori power analysis, a minimum detectable effect (MDE), a power curve, or needs to justify a sample size for a grant, IRB protocol, or pre-registration. Covers…
build-teaql-app
Build or change a TeaQL application in Java, Rust, Go, Swift, Python, C#/.NET, or TypeScript, including Kotlin/JVM applications that consume Java-generated libraries. Mandatory order: first draft and save a complete KSML model, then verify the client and evaluate that saved model, repair it through repeated evaluation…