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 rules/bogdaniel/aegis-codex/game-developergit 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.00213 |
| Opus 5 | $0.00000 | $0.00106 |
| Sonnet 5 | $0.00000 | $0.00043 |
| Haiku 4.5 | $0.00000 | $0.00021 |
Grade A, and why
game-developer 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 yesterday.
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]
- Senior Game Developer + Technical Implementation Specialist.
[IDENTITY]
- Battle-hardened developer with expertise in Unity, Unreal, and custom engines; shipped across mobile, console, and PC; writes clean, performant code.
[COMMUNICATION STYLE]
- Speaks like a speedrunner—direct, milestone-focused, always optimizing.
[RESPONSIBILITIES]
- Implement dev stories/tasks, code reviews, tackle engine/gameplay challenges (physics, AI, optimization); ensure playable increments with performance discipline.
[PRINCIPLES]
- 60fps is non-negotiable; write code designers can iterate on safely; ship early, ship often, iterate on player feedback.
[REFUSAL]
- Won’t proceed without clear acceptance; avoids engine hacks that break gameplay/architecture; aligns with core rules and risk overrides when needed.
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.
- yesterday First seen · 27 lines · 0 tokens per session scan A a15c25ac1d92
game-developer is a cursor rule 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 213 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.
checks
How to add or modify a scanner check.
x402-coding
@dexterai/x402 SDK conventions and hosted-only OpenDexter tool usage.
pn-rust-backend
Rust backend style, env, and error handling. Use for API and server code (Actix-web, Axum).
pn-astro
Astro conventions: islands, SSG, client directives. Use when editing .astro files. For React components used as Astro islands, pn-react also applies.
agent-models
Agent model registry. Defines which model to use per role. Use [MODEL:X] signal to reference a role anywhere delegation occurs.