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-epic)<a href="https://agentmods.dev/commands/webdevtodayjason/titanium-plugins/bmad-epic"><img src="https://agentmods.dev/badge/commands/webdevtodayjason/titanium-plugins/bmad-epic/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-epic"><img src="https://agentmods.dev/badge/commands/webdevtodayjason/titanium-plugins/bmad-epic.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.00008 | $0.01756 |
| Opus 5.5 | $0.00003 | $0.00702 |
| Sonnet 5.5 | $0.00002 | $0.00351 |
| Haiku 4.5 | $0.00001 | $0.00176 |
Grade A, and why
bmad-epic 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 — 257 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BMAD Epic - Generate Epic File
Use the product-manager subagent to create a single epic file with user stories following BMAD methodology. This command is used to add NEW epics to existing backlog or regenerate existing epics.
When to Use This Command
Add NEW Epic (change request, new feature):
# 6 months after launch, need mobile app
/bmad:epic "Mobile App"
# → Creates EPIC-012-mobile-app.md
Regenerate Existing Epic (refinement):
/bmad:epic 3
# → Regenerates EPIC-003 with updated content
NOT used during /bmad:start - guided workflow generates all epics automatically.
Task Delegation
First check prerequisites, determine which epic to generate, then launch the product-manager subagent to handle the complete epic generation workflow.
Process
Step 1: Check Prerequisites
Require PRD:
ls bmad-backlog/prd/prd.md 2>/dev/null || echo "No PRD found"
If not found:
❌ Error: PRD required for epic generation
Please run: /bmad:prd
(Or /bmad:start for complete workflow)
Stop here - do not launch product-manager without PRD.
Check for Architecture (recommended):
ls bmad-backlog/architecture/architecture.md 2>/dev/null || echo "No architecture found"
If not found:
⚠️ Architecture not found
Epic generation works best with architecture (for technical notes).
Would you like to:
1. Generate architecture first (recommended): /bmad:architecture
2. Continue without architecture (epics will have minimal technical notes)
3. Cancel
Choose:
If user chooses 1: Run /bmad:architecture first, then continue
If user chooses 2: Continue to Step 2
If user chooses 3: Exit gracefully
Step 2: Determine Epic to Generate
If user provided epic number:
# User ran: /bmad:epic 3
- Epic number = 3
- Store epic_identifier = "3"
If user provided epic name:
# User ran: /bmad:epic "Mobile App"
- Epic name = "Mobile App"
- Store epic_identifier = "Mobile App"
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 · 257 lines · 8 tokens per session scan A 774fb796222d
bmad-epic is a command published in the GitHub repository webdevtodayjason/titanium-plugins (7 stars, last pushed 8mo ago), licensed MIT. It adds 8 tokens to every session and 1,756 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
template
Manage issue templates for streamlined issue creation.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
add-note
Add an internal or external note to a ConnectWise PSA ticket.
sync-linear
Sync current work with Linear ticket status.
dispatcher
Use when you want the orchestrator to pick the next repo to work on across your whole portfolio — it enumerates candidate repos below the confinement root, resolves free/busy from each repo's session.lock lease, ranks the FREE ones by backlog priority × staleness × readiness, recommends the single most worthwhile one…
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.