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/prdnpx skills add VoxTechnologies/transmute-framework --skill prdgit 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.00087 | $0.02971 |
| Opus 5 | $0.00044 | $0.01486 |
| Sonnet 5 | $0.00017 | $0.00594 |
| Haiku 4.5 | $0.00009 | $0.00297 |
Grade A, and why
prd 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 — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Transmute — PRD Generation (Stage 2)
Read the detailed guide at ${CLAUDE_SKILL_ROOT}/references/prd-detailed-guide.md for the complete agent team architecture, teammate spawn prompts, token budget management, review agent checklists, story grouping examples, and writing guidelines.
Prerequisites
Before starting, verify:
./plancasting/brd/directory exists and contains markdown files. If missing or empty, STOP: "Stage 2 requires completed BRD (Stage 1). Run Stage 1 first."./plancasting/tech-stack.mdexists. If missing, STOP: "Stage 2 requiresplancasting/tech-stack.mdfrom Stage 0. Run Stage 0 first."
Critical Framing
This PRD uses the Full-Build Approach: the COMPLETE product is built and launched as a single release. No MVP, no phased rollout, no feature deferral. P0-P3 priorities define dependency order for parallel development, NOT which features to include or exclude. ALL features ship.
BRD → PRD Relationship
The BRD defines WHAT the business needs. The PRD defines WHAT the product must do and HOW it should behave. Every PRD element must trace back to one or more BRD requirements. The PRD must be detailed enough for engineering, design, and QA teams to begin work without ambiguity.
Execution Flow
Step 1: Read and Analyze Inputs
Read and fully internalize:
- All files in
./plancasting/brd/, including_context.md - All files in
./plancasting/businessplan/for additional context ./plancasting/tech-stack.mdfor stack-informed architecture and API design
Check Session Language in ./plancasting/tech-stack.md. Generate ALL PRD documents in the specified language, matching the BRD's language. Technical identifiers remain in English.
Adapt PRD structure based on product type:
- Mobile: Gesture documentation, platform-specific navigation, native component specs
- IoT/Embedded: Device behavior specs alongside companion app specs
- Desktop: Window management, system tray, keyboard shortcuts
- AI/ML: Model interaction specs (prompts, output formatting, confidence thresholds, fallback)
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 · 180 lines · 87 tokens per session scan A f0e8c26c9f03
prd is a skill published in the GitHub repository VoxTechnologies/transmute-framework (4 stars, last pushed 1mo ago), licensed MIT. It adds 87 tokens to every session and 2,971 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
release
Prepare and publish Perigon.CLI patch releases, including versioning, release notes, bilingual docs, validation, and the nuget-branch CI handoff.
error-message-explainer
Explain Arduino and embedded compiler, upload, boot, power, and runtime errors in plain English. Use when a user shares an error or failure from Arduino IDE, Arduino CLI, PlatformIO, or a vendor-specific tool. Separate build, upload, hardware, and system evidence and give a board-specific recovery path without…
blazor
Use for Blazor Server development with Fluent UI Blazor, Razor components, layouts, pages, scoped UI services, culture switching, localization, forms, loading/empty/error states, and Studio-style dashboard workflows.
cli
Use for .NET command-line tool development with Spectre.Console/Spectre.Console.Cli, Microsoft.Extensions.Hosting, dependency injection, localized help text, command settings, aliases, examples, terminal output, exit codes, and stdio-safe command paths.
rn-publishing-payments
Use when preparing an Expo + RN app for store submission (metadata, screenshots, localized listings, privacy nutrition label, age rating) and integrating monetization (In-App Purchases via RevenueCat for digital goods/subscriptions; Stripe via WebView ONLY for non-digital services). Triggers on: "submit to App Store"…
rn-animations-gestures
Use when adding animations or gestures to a React Native + Expo app: scale/opacity/translation transitions, layout animations (FadeIn/SlideIn/FadeOut), shared-value driven motion, swipe-to-delete, pan/pinch/long-press gestures, scroll-linked animations. Triggers on: "anima questo", "swipe to X", "fade in/out", "pinch…