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 skills add DDS-Solutions/AI-TadPole-OS --skill game-developmentgit clone --depth 1 https://github.com/DDS-Solutions/AI-TadPole-OSWrote 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/skills/dds-solutions/ai-tadpole-os/game-development)<a href="https://agentmods.dev/skills/dds-solutions/ai-tadpole-os/game-development"><img src="https://agentmods.dev/badge/skills/dds-solutions/ai-tadpole-os/game-development.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00018 | $0.00680 |
| Opus 5 | $0.00009 | $0.00340 |
| Sonnet 5 | $0.00004 | $0.00136 |
| Haiku 4.5 | $0.00002 | $0.00068 |
Grade A, and why
game-development 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 7d 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
[!IMPORTANT] AI Context & Knowledge Heritage
- Subsystem: Agent Skills Registry / game-development
- Architecture:
@docs ARCHITECTURE:Documentation- Failure Path: Information drift, legacy terminology, or documentation mismatch.
- Observability: Traceability via
execution/parity_guard.py([SKILL])
Game Development Orchestrator
Role: Core game architecture and routing hub for platform-specific and genre-specific game sub-skills.
🎯 Progressive Disclosure & Sub-Skill Directory
Read REQUIRED core loop rules below; load specialized Sub-Skills on demand:
| Domain / Target | Sub-Skill Directory | Focus / Technologies |
|---|---|---|
| Web Games | web-games/SKILL.md |
HTML5, Canvas, WebGL, PixiJS, Three.js, Phaser |
| Mobile Games | mobile-games/SKILL.md |
Touch controls, battery optimization, iOS/Android |
| PC Games | pc-games/SKILL.md |
Steam integration, high-poly assets, desktop performance |
| 2D Systems | 2d-games/SKILL.md |
Sprites, tilemaps, 2D physics, pixel art |
| 3D Systems | 3d-games/SKILL.md |
Shaders, meshes, spatial lighting, PBR materials |
| Multiplayer | multiplayer/SKILL.md |
Client prediction, server reconciliation, lag compensation |
| Game Design & Audio | game-design/SKILL.md, game-audio/SKILL.md |
GDD, balance economics, spatial audio, adaptive sound |
🔄 1. The Universal Game Loop & Timestep
1. INPUT ➔ Sample abstracted action bindings (e.g. "jump", "fire").
2. UPDATE ➔ Advance physics & state at a deterministic fixed timestep (e.g. 50Hz / 20ms).
3. RENDER ➔ Interpolate state between ticks and draw to screen (60 FPS = 16.6ms budget).
⚡ 2. Core Architectural Patterns
- Object Pooling: Mandatory for high-frequency spawns (projectiles, particle effects).
- State Machines: Use finite state machines (FSM) for character states (Idle ➔ Run ➔ Jump).
- Action Abstraction: Map actions (
"interact") rather than physical hardware keys (KeyE).
What ships with it
10 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago First seen · 51 lines · 18 tokens per session scan A 2bb14cb1f0f3
game-development is a skill published in the GitHub repository DDS-Solutions/AI-TadPole-OS (8 stars, last pushed 2d ago), licensed MIT. It adds 18 tokens to every session and 680 once invoked, about $0.0001 per session on Opus 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-08-31.
Other skills, from other repositories
airjam-mcp
Use when operating an Air Jam project through its first-party MCP tools for inspection, development, semantic game sessions, logs, quality gates, and releases.
controller-ui
Use when building or reviewing Air Jam controller surfaces so touch controls stay simple, readable, and game-appropriate instead of drifting into dense web-app UI patterns.
host-surface
Use when building or reviewing the Air Jam host shell so the active game surface stays full-frame, overlays stay modular, and host UI does not interfere with gameplay layout.
game-architecture
Use when creating or refactoring gameplay code in an Air Jam project and you need guidance on host vs controller vs domain boundaries, modular structure, and when to refactor before implementing.
prefab-authoring
Use when creating reusable gameplay objects or scene presets so prefabs stay declarative, configurable, and ready for future tooling such as previews and scanned catalogs.
r3f-3d-scene
Use when building or reviewing a 3D Air Jam game with React Three Fiber so scene structure, lighting, shadows, grounding, particles, and physics stay deliberate instead of becoming ad hoc Three.js chaos.