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.
git clone --depth 1 https://github.com/webdevtodayjason/titanium-pluginsWrote 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/commands/webdevtodayjason/titanium-plugins/bmad-prd)<a href="https://agentmods.dev/commands/webdevtodayjason/titanium-plugins/bmad-prd"><img src="https://agentmods.dev/badge/commands/webdevtodayjason/titanium-plugins/bmad-prd/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/commands/webdevtodayjason/titanium-plugins/bmad-prd"><img src="https://agentmods.dev/badge/commands/webdevtodayjason/titanium-plugins/bmad-prd.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.00006 | $0.02270 |
| Opus 5.5 | $0.00002 | $0.00908 |
| Sonnet 5.5 | $0.00001 | $0.00454 |
| Haiku 4.5 | $0.00001 | $0.00227 |
Grade A, and why
bmad-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 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 — 360 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BMAD PRD - Generate Product Requirements Document
Use the product-manager subagent to create a comprehensive Product Requirements Document (PRD) following BMAD methodology.
Task Delegation
First check for product brief, then launch the product-manager subagent to handle the complete PRD generation workflow.
Process
Step 1: Check for Product Brief
ls bmad-backlog/product-brief.md 2>/dev/null || echo "No brief found"
If brief NOT found:
❌ Error: Product Brief not found at bmad-backlog/product-brief.md
PRD generation requires a product brief to work from.
Please run: /titanium-toolkit:bmad-brief first
(Or /titanium-toolkit:bmad-start for complete guided workflow)
Stop here - do not launch product-manager without brief.
If brief exists: Continue to Step 2.
Step 2: Launch Product-Manager Subagent
Use the Task tool to launch the product-manager subagent in its own context window:
Task(
description: "Generate BMAD PRD",
prompt: "Create comprehensive Product Requirements Document following BMAD methodology.
Input:
- Product Brief: bmad-backlog/product-brief.md
Output:
- PRD: bmad-backlog/prd/prd.md
Your workflow:
1. **Read the product brief** to understand the project vision
2. **Generate PRD** using the MCP tool:
mcp__plugin_titanium-toolkit_tt__bmad_generator( doc_type: "prd", input_path: "bmad-backlog/product-brief.md", project_path: "$(pwd)" )
3. **Review epic structure** - Ensure Epic 1 is \"Foundation\" and epic sequence is logical
4. **Detect research needs** - Scan for API, vendor, data source, payment, hosting keywords
5. **Validate PRD** using:
mcp__plugin_titanium-toolkit_tt__bmad_validator( doc_type: "prd", document_path: "bmad-backlog/prd/prd.md" )
6. **Run vibe-check** to validate PRD quality and completeness
7. **Store in Pieces** for future reference
8. **Present summary** with epic list, research needs, and next steps
**IMPORTANT**: Keep your summary response BRIEF (under 500 tokens). Just return:
- Confirmation PRD is complete
- Epic count and list (just titles)
- Total user stories count
- Total features count
DO NOT include the full PRD content in your response - it's already saved to the file.
Follow your complete PRD workflow from the bmad-methodology skill.
Project path: $(pwd)",
subagent_type: "product-manager"
)
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 · 360 lines · 6 tokens per session scan A db9814719680
bmad-prd is a command published in the GitHub repository webdevtodayjason/titanium-plugins (7 stars, last pushed 8mo ago), licensed MIT. It adds 6 tokens to every session and 2,270 once invoked, about $0.0000 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-08-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.