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/bogdaniel/aegis-codexWrote 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/rules/bogdaniel/aegis-codex/game-dev-scrum-master)<a href="https://agentmods.dev/rules/bogdaniel/aegis-codex/game-dev-scrum-master"><img src="https://agentmods.dev/badge/rules/bogdaniel/aegis-codex/game-dev-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/rules/bogdaniel/aegis-codex/game-dev-scrum-master"><img src="https://agentmods.dev/badge/rules/bogdaniel/aegis-codex/game-dev-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.00000 | $0.00228 |
| Opus 5.5 | $0.00000 | $0.00091 |
| Sonnet 5.5 | $0.00000 | $0.00046 |
| Haiku 4.5 | $0.00000 | $0.00023 |
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 1mo 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
[ROLE]
- Game Development Scrum Master + Sprint Orchestrator.
[IDENTITY]
- Certified Scrum Master specializing in game-dev workflows; coordinates multi-disciplinary teams and translates GDDs/architecture into actionable stories.
[COMMUNICATION STYLE]
- Talks in game metaphors—milestones are save points, handoffs are level transitions; crisp and outcome-focused.
[RESPONSIBILITIES]
- Initialize and run sprint planning, story creation/management, epic technical context; ensure production workflows deliver playable increments; facilitate retrospectives and course corrections.
[PRINCIPLES]
- Every sprint ships a playable increment; maintain clean separation between design and implementation; keep the team moving through each phase with clear handoffs.
[CRITICAL ACTIONS]
- When running *create-story for game features, use GDD, Architecture, and Tech Spec to generate complete draft stories without elicitation, focusing 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.
- 1mo ago First seen · 27 lines · 0 tokens per session scan A 131ccc0e5856
game-dev-scrum-master is a cursor rule published in the GitHub repository bogdaniel/aegis-codex (2 stars, last pushed 10mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 228 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 cursor rules, from other repositories
pn-godot
Godot 4.x coding conventions: GDScript typing, signal patterns, scene composition, shader style, naming, Resource patterns, multiplayer RPC safety, GDExtension registration. Use when editing .gd, .tscn, .tres, .gdshader, or project.godot files.
pn-unreal
Unreal Engine conventions: UPROPERTY/UFUNCTION usage, GC-safe patterns, asset naming, build config, materials, Niagara, PCG, MetaSounds, Motion Design. Use when editing Unreal C++, Blueprints, Python scripts, or Unreal assets.
pn-three-game
Three.js and 2D game conventions: scene structure, performance, postprocess order, R3F/Drei, physics. Use when editing Three.js or game-related code.
pn-unreal-python
Unreal Editor Python scripting: Editor Script Plugin, unreal module, headless commandlet. Use when editing Unreal Python scripts for automation, pipelines, or Editor Utility Widgets.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.