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 skills add alvin-reyes/better-agentic-ide --skill bmad-ticketgit clone --depth 1 https://github.com/alvin-reyes/better-agentic-ideWrote 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/skills/alvin-reyes/better-agentic-ide/bmad-ticket)<a href="https://agentmods.dev/skills/alvin-reyes/better-agentic-ide/bmad-ticket"><img src="https://agentmods.dev/badge/skills/alvin-reyes/better-agentic-ide/bmad-ticket/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/skills/alvin-reyes/better-agentic-ide/bmad-ticket"><img src="https://agentmods.dev/badge/skills/alvin-reyes/better-agentic-ide/bmad-ticket.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.00091 | $0.02450 |
| Opus 5.5 | $0.00036 | $0.00980 |
| Sonnet 5.5 | $0.00018 | $0.00490 |
| Haiku 4.5 | $0.00009 | $0.00245 |
Grade A, and why
bmad-ticket 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 today.
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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BMad Ticket
What you are here to do
You are the facilitator: help the user turn their intent into tickets a coding agent can build from. The user decides the scope and split; you propose boundaries, explain tradeoffs, and check coverage. Use the context already supplied, ask unresolved questions that affect the work, and develop the breakdown with them.
When the user asks you to do the thinking without the conversation, the same guidance, self-review, and subagents apply. Gaps become open questions in Notes and choices become marked assumptions, never silent guesses. The check on a draft in references/validate.md always runs. Before publish, ask once which other validations to run unless already said, and still get a yes to publish unless they said to publish too.
Terms
- Container: an initiative or an epic — holds other tickets
- Envelope: a container's file before its children are planned — intent, Outcome, Done when, boundaries, known decisions, references
- Leaf: a story, spike, or bug handed to an agent to implement. Under an epic a story is an implementation slice sequenced to reach the epic's Done when, not a user-value slice; an enabler, or work a person must do (hitl), is a story
- Breakdown:
tickets.tomlbeside a container's ticket file — its agreed children, in build order, with the prerequisitestickets.pyreads - Entry: one planned leaf in a breakdown, with a stable
id: description, requirement ids (covers), prerequisites (after), verification approach, and known uncertainty. It needs no file to be built: the build reads the entry and its epic. With no file and no plan its state isplanned - Pull: write an entry's leaf file with
tickets.py pull, the first step of reviewing it, refining it, or publishing it to a tracker. Starting a ticket needs no pull - Refine: expand a ticket to full acceptance criteria before it starts — a bug, a ticket with no epic, or an entry with
refine = true. Any other story goes to the build as it is; the user can ask to review one first in its pulled file - Inception: plan the whole selected epic with the user and record it in the epic's breakdown
- hitl: boolean frontmatter field on a leaf; at least part needs a person
- store: the ticketing system of record — git-backed, a tracker, or both
- State:
planned,backlog,in-progress,review,done, ordropped— what the board groups by and what a tracker sees. Everytickets.pyrow carries its ticket'sstate; use it rather than deriving it
What ships with it
24 files 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.
- assets/bug-template.md 4.8 KB
- assets/epic-template.md 5.2 KB
- assets/initiative-template.md 5.4 KB
- assets/spike-template.md 5.1 KB
- assets/story-template.md 5.2 KB
- assets/tickets-template.toml 3.2 KB
- bmod.toml 113 B
- config/github-ticketing.toml 4.6 KB
- config/jira-ticketing.toml 4.8 KB
- config/linear-ticketing.toml 4.0 KB
- config/notion-ticketing.toml 4.0 KB
- config/repo-ticketing.toml 2.6 KB
- config/trello-ticketing.toml 3.7 KB
- customize.toml 3.1 KB
- references/board.md 12 KB
- references/slice.md 13 KB
- references/store-setup.md 2.9 KB
- references/ticket.md 9.9 KB
- references/validate-checks.md 4.7 KB
- references/validate.md 2.3 KB
- scripts/read_store.py 4.6 KB runs code
- scripts/tests/test_read_store.py 5.4 KB runs code
- scripts/tests/test_tickets.py 85 KB runs code
- scripts/tickets.py 64 KB runs code
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.
- today First seen · 105 lines · 91 tokens per session scan A 8c34900947df
bmad-ticket is a skill published in the GitHub repository alvin-reyes/better-agentic-ide (85 stars, last pushed 9d ago), licensed MIT. It adds 91 tokens to every session and 2,450 once invoked, about $0.0004 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-10-26.
Other skills, from other repositories
vigilante-create-issue
Help a human author write an implementation-ready GitHub issue that Vigilante can execute reliably.
kano-backlog
Prioritize and refine a GitHub Issues backlog with the Kano model — categorize every open issue as Must-be, Performance, Attractive, Indifferent, or Reverse, apply Kano + priority labels back to GitHub automatically, and recommend the single best next issue to pick up. Use this whenever the user wants to triage…
vigilante-issue-implementation
Implement a GitHub issue end-to-end when Vigilante dispatches work for a watched repository. Use the provided worktree, respect repository instructions, comment on the issue as work progresses, and report failures back to GitHub.
vigilante-issue-implementation-on-bazel-monorepo
Implement a GitHub issue end-to-end when Vigilante dispatches work for a Bazel-based monorepo. Use the provided worktree, respect repository instructions, comment on the issue as work progresses, and report failures back to GitHub.
vigilante-issue-implementation-on-rush-monorepo
Implement a GitHub issue end-to-end when Vigilante dispatches work for a watched Rush monorepo. Use the provided worktree, respect repository instructions, comment on the issue as work progresses, and report failures back to GitHub.
vigilante-issue-implementation-on-turborepo
Implement a GitHub issue end-to-end when Vigilante dispatches work for a pnpm/workspace-based Turborepo. Use the provided worktree, respect repository instructions, comment on the issue as work progresses, and report failures back to GitHub.