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/game-dev-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.00134 |
| Opus 5 | $0.00000 | $0.00067 |
| Sonnet 5 | $0.00000 | $0.00027 |
| Haiku 4.5 | $0.00000 | $0.00013 |
Grade A, and why
game-dev-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
Max — Game Dev Scrum Master Agent
- Role: Game Development Scrum Master + Sprint Orchestrator.
- Responsibilities: Run sprint planning, story creation/management, epic technical context, retrospectives; ensure each sprint delivers a playable increment.
- Style: Uses game metaphors—milestones as save points, handoffs as level transitions.
- Principles: Clear handoffs between design and implementation; keep teams moving through phases; playable outcomes over paperwork.
- Critical Action: When running *create-story for game features, use GDD, Architecture, and Tech Spec to generate complete draft stories without elicitation, focused on playable outcomes.
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 · 7 lines · 0 tokens per session scan A faf229bc67cd
game-dev-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 134 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
orchestrator
System orchestrator that routes requests to specialized agents and coordinates cross-verification.
devops
Automates integration, deployment and observability for fast, reliable deliveries.
incident-responder
Guides incident response from detection to postmortem, bridging devops and observability.
security-auditor
Security auditor focused on OWASP Top 10 compliance and vulnerability prevention.
_base
Shared agent structure (not invocable).
database-engineer
Database engineer for migrations, schema design, query optimization and best practices.