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-index)<a href="https://agentmods.dev/commands/webdevtodayjason/titanium-plugins/bmad-index"><img src="https://agentmods.dev/badge/commands/webdevtodayjason/titanium-plugins/bmad-index/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-index"><img src="https://agentmods.dev/badge/commands/webdevtodayjason/titanium-plugins/bmad-index.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.01327 |
| Opus 5.5 | $0.00002 | $0.00531 |
| Sonnet 5.5 | $0.00001 | $0.00265 |
| Haiku 4.5 | $0.00001 | $0.00133 |
Grade A, and why
bmad-index 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 — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BMAD Index - Generate Story Index
Use the product-manager subagent to generate a STORY-INDEX.md file that summarizes all epics and user stories in the backlog. This provides a quick overview for sprint planning and progress tracking.
Purpose
Create a summary table showing:
- Total epics, stories, and story points
- Epic overview with story counts
- Per-epic story details
- Priority distribution
- Development phases
When to Use
- After
/bmad:startcompletes (auto-generated) - After adding new epic with
/bmad:epic - After manually editing epic files
- Want refreshed totals and summaries
- Planning sprints
Task Delegation
First check that epics exist, then launch the product-manager subagent to handle the complete index generation workflow.
Process
Step 1: Check for Epics
ls bmad-backlog/epics/EPIC-*.md 2>/dev/null || echo "No epics found"
If no epics found:
❌ No epic files found
Story index requires epic files to summarize.
Please generate epics first:
- Run: /bmad:epic 1
- Or: /bmad:start (complete workflow)
Stop here - do not launch product-manager without epic files.
If epics found: 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 story index",
prompt: "Create comprehensive story index summarizing all epics and user stories.
Input:
- Epic files: bmad-backlog/epics/EPIC-*.md
Output:
- Story index: bmad-backlog/STORY-INDEX.md
Your workflow:
1. **Generate story index** using MCP tool:
mcp__plugin_titanium-toolkit_tt__bmad_generator( doc_type: "index", input_path: "bmad-backlog/epics/", project_path: "$(pwd)" )
2. **Review generated index**:
- Read bmad-backlog/STORY-INDEX.md
- Extract totals (epics, stories, story points)
- Extract epic breakdown
- Extract priority distribution
3. **Present summary** with key metrics:
- Total epics, stories, story points
- Epic breakdown with story counts per epic
- Priority distribution (P0/P1/P2 percentages)
- Show sample from index (epic overview table)
4. **Run vibe-check** to validate index quality
5. **Store in Pieces** for future reference:
- Include index file
- Include all epic files
- Summarize totals and breakdown
6. **Suggest next steps**:
- Sprint planning guidance
- Implementation readiness
- Progress tracking tips
Follow your complete index 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 · 214 lines · 6 tokens per session scan A 65e022c1dda9
bmad-index 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 1,327 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.