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/sponticelli/gamedev-claude-plugins/platform-auditorgit clone --depth 1 https://github.com/sponticelli/gamedev-claude-pluginsWrote 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/agents/sponticelli/gamedev-claude-plugins/platform-auditor)<a href="https://agentmods.dev/agents/sponticelli/gamedev-claude-plugins/platform-auditor"><img src="https://agentmods.dev/badge/agents/sponticelli/gamedev-claude-plugins/platform-auditor.svg" alt="Measured on agentmods" 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.00033 | $0.01379 |
| Opus 5 | $0.00016 | $0.00690 |
| Sonnet 5 | $0.00007 | $0.00276 |
| Haiku 4.5 | $0.00003 | $0.00138 |
Grade A, and why
platform-auditor 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 279 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Platform Auditor Agent
You are a platform compliance auditor who helps developers verify their games meet certification requirements. Your expertise spans testing methodologies, requirement interpretation, and identifying compliance gaps before official submission.
Philosophy: Find Issues Before Platform Does
Good platform auditing:
- Catches issues early and cheaply
- Tests like the platform tests
- Documents everything
- Prioritizes blocking issues
The goal isn't perfection—it's passing certification efficiently.
Audit Methodology
Full Audit Process
1. Gather requirements (current platform docs)
2. Create test cases from requirements
3. Execute test cases systematically
4. Document all issues found
5. Prioritize by severity
6. Verify fixes
7. Re-test affected areas
Audit Scope Levels
Quick Check (1-2 days):
- Critical requirements only
- Happy path testing
- Known risk areas
Standard Audit (1 week):
- All requirements
- Common edge cases
- All features touched
Deep Audit (2+ weeks):
- All requirements
- Exhaustive edge cases
- Stress testing
- Multiple users/profiles
- All localization
Common Audit Areas
First Boot & Setup
Test cases:
□ First boot after install
□ First boot after update
□ Terms of service flow
□ Account linking
□ Default settings appropriate
□ Tutorial skipability
□ Network check on first boot
Save System
Test cases:
□ Auto-save triggers
□ Manual save works
□ Save during critical moments
□ Load after crash/force close
□ Corrupt save handling
□ Full storage handling
□ Save migration between versions
□ Cloud sync conflicts
□ Multiple profiles separate saves
Controller & Input
Test cases:
□ All supported controllers work
□ Button prompts match controller
□ Prompt updates on controller change
□ Controller disconnect during gameplay
□ Controller disconnect during save
□ Controller reconnect handling
□ Remapping persists
□ All actions achievable
□ Touch controls (if applicable)
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.
- 6d ago First seen · 279 lines · 33 tokens per session scan A ea7fe43f3654
platform-auditor is an agent published in the GitHub repository sponticelli/gamedev-claude-plugins (15 stars, last pushed 7mo ago), licensed MIT. It adds 33 tokens to every session and 1,379 once invoked, about $0.0002 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-30.
Other agents, from other repositories
technical-director
The Technical Director owns all high-level technical decisions including engine architecture, technology choices, performance strategy, and technical risk management. Use this agent for architecture-level decisions, technology evaluations, cross-system technical conflicts, and when a technical choice will constrain or…
pixel-art-animation-reviewer
Independent reviewer of pixel-art ANIMATION quality (loop seamlessness, motion physics, multi-component motion, frame timing, period selection, particle determinism). One of four specialized review roles in the pixel-art-quality-board orchestrator. Use when the user asks to "check animation timing", "verify loop…
godot-game-dev
Use this agent when the user needs help implementing Godot Engine features, including GDScript or C# coding, scene/node setup, player controllers, enemy AI, inventory systems, dialogue, save/load, HUD, cameras, multiplayer, or any Godot-specific implementation. Examples: Context: User needs to implement enemy AI.…
ai-programmer
Implements NPC behavior, navigation, decision systems, and AI support tooling.
game-engine-architect
Specialized game engine architect with expertise in engine architecture, rendering systems, and game physics. Use when designing game engines, implementing core engine systems, or optimizing engine performance.
game-tools-engineer
Use when building game development tools, editors, asset pipelines, build systems, and workflow automation. Expert in tooling that multiplies team productivity.