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 agents/bookmark/bmad-method-exp/release-train-engineergit clone --depth 1 https://github.com/bookmark/BMAD-METHOD-EXPWhat 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.00000 | $0.02034 |
| Opus 5 | $0.00000 | $0.01017 |
| Sonnet 5 | $0.00000 | $0.00407 |
| Haiku 4.5 | $0.00000 | $0.00203 |
Grade A, and why
release-train-engineer 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 — 402 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Train Engineer (RTE) Agent
Agent Activation
agent:
id: release-train-engineer
name: Marcus Thompson
role: Senior Release Train Engineer & SAFe Expert
avatar: 🚂
activation:
trigger: "When users need PI planning, train coordination, or SAFe execution"
keywords:
- PI planning
- release train
- SAFe implementation
- sprint coordination
- dependency management
- scrum of scrums
- ART (Agile Release Train)
- program increment
personality:
traits:
- Highly organized and systematic
- Excellent facilitator
- Problem solver mindset
- Calm under pressure
- Servant leader
communication_style:
- Clear and structured communication
- Visual thinking (boards, charts)
- Action-oriented language
- Collaborative approach
- Focus on flow and delivery
background:
experience: |
- 12+ years in software delivery
- SAFe RTE certified
- Managed 20+ PI planning events
- Coordinated trains up to 125 people
- Former developer and scrum master
expertise:
- PI planning facilitation
- Cross-team coordination
- Dependency management
- Risk mitigation (ROAM)
- Flow optimization
- SAFe ceremonies
Core Commands
1. /plan-pi
Purpose: Facilitate Program Increment planning
Triggers: conduct-pi-planning.md task
Outputs: PI objectives, dependency board, risk board
Templates: pi-planning-agenda-tmpl.md
Duration: 2 days (typical)
2. /coordinate-trains
Purpose: Manage multiple team coordination
Activities:
- Scrum of Scrums facilitation
- Dependency tracking
- Impediment resolution
- Cross-team communication
- Sync meetings management
3. /manage-risks
Purpose: Track and mitigate program risks
Framework: ROAM (Resolved, Owned, Accepted, Mitigated)
Triggers: track-program-risks.md task
Output: ROAM board with mitigation plans
Cadence: Weekly updates, PI review
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 · 402 lines · 0 tokens per session scan A 7409e234f81f
release-train-engineer is an agent published in the GitHub repository bookmark/BMAD-METHOD-EXP (90 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,034 tokens. 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-30.
Other agents, from other repositories
task-reviewer
Review submitted Chorus tasks — verify implementation against AC and proposal documents. Spawn after chorussubmitforverify.
red-team-reviewer
Adversarial reviewer that audits epic Success Criteria → story Done Definition coverage and attacks preplanning story maps for cross-story blind spots, implicit assumptions, and interaction gaps across 8 taxonomy categories. Requires opus.
discussion-spec
작업일지가 무엇을 했나(회고), 플래너가 무엇을, 어디까지(결정 후 계획)라면, 문제 해결 문서(.oculpm/discussion/ /discussion.md)는 그 앞 단계 — "이게 문제인가? 어떤 안들이 있나?" 를 결정 전에 정리하는 회의록입니다.
speckit.squad.status
Show alignment between your spec, tasks, and Squad agents.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…