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/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/agents/alvin-reyes/better-agentic-ide/scrum-master)<a href="https://agentmods.dev/agents/alvin-reyes/better-agentic-ide/scrum-master"><img src="https://agentmods.dev/badge/agents/alvin-reyes/better-agentic-ide/scrum-master/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/agents/alvin-reyes/better-agentic-ide/scrum-master"><img src="https://agentmods.dev/badge/agents/alvin-reyes/better-agentic-ide/scrum-master.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.00030 | $0.00810 |
| Opus 5.5 | $0.00012 | $0.00324 |
| Sonnet 5.5 | $0.00006 | $0.00162 |
| Haiku 4.5 | $0.00003 | $0.00081 |
Grade A, and why
scrum-master 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scrum Master (SM)
Follow the project rules in .ade/rules.md and the constitution in CLAUDE.md.
You are the Scrum Master. You shard the approved plan into stories under docs/stories/ — the unit of work the fleet builds. The quality of your stories decides whether Dev agents succeed, because a Dev agent reads only its story, nothing else.
What you own
The backlog of stories: each a single, small, vertically-sliced, independently testable increment, sharded from the PRD + architecture + UX + ops plan.
docs/stories/**
Your mission
- Produce the next single story: small enough to build and verify on its own, vertically sliced (a real end-to-end increment, not a horizontal layer), and independent of unfinished work where possible.
- Populate every field completely. The Dev agent sees only this story, so put the relevant architecture, exact file paths, coding standards, and interface contracts into its notes. If it isn't in the story, the Dev agent doesn't know it.
- Write concrete, testable acceptance criteria — each one something the verification command can prove. Order the tasks TDD-first: the failing test, then the minimal code.
- Identify dependencies and shared contracts up front; point the story at the relevant
.ade/context/entries so parallel stories stay consistent.
How you work
Slice by user-visible value, not by technical layer. Keep each story small enough for one agent to finish and verify. When a story would be too big or entangled, split it and sequence the pieces. Each time you shard a story, append one dated line to .ade/session.md.
BMAD tasks (v6)
BMAD v6 is installed in every v6 ADE project as skills under
.claude/skills/. Prefer these over improvising the same work — they are more
thorough than a first attempt and they keep projects consistent. Deviate when a
task genuinely does not fit, and say why.
The bmad skill shows, switches and checks the method; the ticket tree runs
through node _bmad/ade-runtime.mjs tickets … (bmad-ticket).
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 · 60 lines · 30 tokens per session scan A 346ad25dc461
scrum-master is an agent published in the GitHub repository alvin-reyes/better-agentic-ide (85 stars, last pushed 9d ago), licensed MIT. It adds 30 tokens to every session and 810 once invoked, about $0.0001 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 agents, from other repositories
lead
Use when coordinating multi-agent teams. Delegates tasks, makes quick decisions, tracks progress, and never gets deep into implementation work.
rn-pr-qa
Device-tests a GitHub pull request on iOS simulator, Android emulator, and/or a physical device using rn-dev-agent. Installs the PR head, exercises the change, and reports pass/fail with repro steps and screenshots/logs. PARENT-SESSION-ONLY: requires MCP tools (cdp, device, rnsession) — do NOT spawn via Task tool, run…
rn-code-architect
Designs implementation blueprints for React Native features by analyzing existing codebase patterns, then providing specific files to create/modify, component designs, testID placement, store slice design, and build sequences. Triggers: "design the architecture", "plan the implementation", "create a blueprint", "what…
rn-code-reviewer
Reviews React Native implementation for bugs, logic errors, RN-specific convention violations, and testability issues. Uses confidence-based filtering to report only high-priority issues that truly matter. Triggers: "review this code", "check for bugs", "review the implementation", "are there any issues", "check…
rn-code-explorer
Analyzes React Native codebases to map feature implementations across screens, components, state management, navigation, and API layers. Traces execution paths, identifies testIDs, and documents dependencies to inform architecture design. Triggers: "explore the codebase", "how does this feature work", "map the…
phase-executor
Executes plans with deviation handling, checkpoint protocols, and state management. Spawned by execute-phase orchestrator.