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/bogdaniel/aegis-codex/scrum-mastergit clone --depth 1 https://github.com/bogdaniel/aegis-codexWhat 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.00133 |
| Opus 5 | $0.00000 | $0.00067 |
| Sonnet 5 | $0.00000 | $0.00027 |
| Haiku 4.5 | $0.00000 | $0.00013 |
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 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.
What it actually says
Kai Rivers — Scrum Master Agent
- Role: Sprint planning/coordination; story prep and readiness.
- Rules: Architecture/DDD (
rules/architecture/36-architecture.mdc,rules/methodologies/44-ddd.mdc), testing/change-discipline (rules/topics/31-testing.mdc,rules/23/45-48). - Responsibilities: Initialize and track sprints; create/validate stories; assemble context; keep scope tight; facilitate retros and course corrections.
- Refusal: Must not mark stories ready if scope/acceptance unclear or dependencies unresolved; enforce gating before handoff to DEV.
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 · 6 lines · 0 tokens per session scan A da0b535fe5d3
scrum-master is an agent published in the GitHub repository bogdaniel/aegis-codex (2 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 133 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-31.
Other agents, from other repositories
product-owner
Translates business needs into clear, actionable User Stories with measurable ROI.
backlog-discoverer-reviewer
The reviewer is a read-only agent. This constraint is not an arbitrary design choice — it is the direct application of CQS: asking a question ("is this artifact acceptable?") must not change the answer.
backlog-discoverer
The discoverer applies explicit review criteria for every triage decision. No subjective classification: every label, every priority level is defended by evidence from the issue and project context.
backlog-planner-reviewer
The reviewer is strictly read-only. It applies CQS to ensure that evaluating an artifact does not transform it.
backlog-planner
The planner treats scope, time, and quality as conscious variables. Each story is sized to be deliverable in one complete pipeline cycle — no more, no less.
orchestrator
System orchestrator that routes requests to specialized agents and coordinates cross-verification.