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/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/commands/sponticelli/gamedev-claude-plugins/compliance-audit)<a href="https://agentmods.dev/commands/sponticelli/gamedev-claude-plugins/compliance-audit"><img src="https://agentmods.dev/badge/commands/sponticelli/gamedev-claude-plugins/compliance-audit/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/commands/sponticelli/gamedev-claude-plugins/compliance-audit"><img src="https://agentmods.dev/badge/commands/sponticelli/gamedev-claude-plugins/compliance-audit.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.00012 | $0.00920 |
| Opus 5 | $0.00006 | $0.00460 |
| Sonnet 5 | $0.00002 | $0.00184 |
| Haiku 4.5 | $0.00001 | $0.00092 |
Grade A, and why
compliance-audit 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 9d 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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Compliance Audit Generator
Create a compliance audit report against platform requirements.
Context Gathering
Before generating the audit, understand the context:
Identify Scope
- Which platform requirements?
- Full audit or specific areas?
- Current build version?
- Previous audit results?
Understand Current State
- What's been tested?
- Known issues?
- Recent changes?
- Fix verification needed?
Check Resources
- Test hardware available?
- Test accounts set up?
- Documentation accessible?
- Time allocation?
Identify Focus Areas
- High-risk features?
- Previously failed areas?
- New features since last audit?
- Regression testing needed?
Use this context to create focused audit.
Output Format
# Compliance Audit Report
## Audit Information
**Platform:** [Platform name]
**Requirements version:** [TRC/XR version]
**Build tested:** [Build number]
**Test date:** [Date]
**Auditor:** [Name]
**Scope:** [Full/Focused on X]
## Executive Summary
**Recommendation:** [Ready/Not ready for submission]
| Category | Pass | Fail | Waiverable | N/A |
|----------|------|------|------------|-----|
| System | [N] | [N] | [N] | [N] |
| Input | [N] | [N] | [N] | [N] |
| Network | [N] | [N] | [N] | [N] |
| Platform | [N] | [N] | [N] | [N] |
| Content | [N] | [N] | [N] | [N] |
| **Total** | **[N]** | **[N]** | **[N]** | **[N]** |
## Blocking Issues
### [Issue ID]: [Issue Title]
**Requirement:** [TRC/XR number]
**Severity:** [Critical/Major]
**Category:** [System/Input/Network/etc.]
**Description:**
[What the issue is]
**Steps to Reproduce:**
1. [Step 1]
2. [Step 2]
3. [Step 3]
**Expected Result:**
[What should happen]
**Actual Result:**
[What happens]
**Evidence:**
[Screenshot/video reference]
**Recommendation:**
[How to fix]
---
[Repeat for each blocking issue]
## Non-Blocking Issues
### [Issue ID]: [Issue Title]
**Requirement:** [TRC/XR number]
**Severity:** [Minor]
**Waiverable:** [Yes/No/Maybe]
**Description:**
[Brief description]
**Waiver justification (if applicable):**
[Why this could be waived]
---
[Repeat for each non-blocking issue]
## Passed Areas
### System Features
| Test | Result | Notes |
|------|--------|-------|
| [Test case] | Pass | [Any notes] |
### Input/Controller
| Test | Result | Notes |
|------|--------|-------|
| [Test case] | Pass | [Any notes] |
### Network
| Test | Result | Notes |
|------|--------|-------|
| [Test case] | Pass | [Any notes] |
### Platform Features
| Test | Result | Notes |
|------|--------|-------|
| [Test case] | Pass | [Any notes] |
### Content
| Test | Result | Notes |
|------|--------|-------|
| [Test case] | Pass | [Any notes] |
## Not Tested
| Area | Reason |
|------|--------|
| [Area] | [Why not tested] |
## Recommendations
### Before Submission
1. [Must fix issue 1]
2. [Must fix issue 2]
### Should Fix If Time Allows
1. [Issue 1]
2. [Issue 2]
### Future Considerations
1. [Suggestion 1]
2. [Suggestion 2]
## Test Environment
| Parameter | Value |
|-----------|-------|
| Hardware | [Model] |
| Firmware | [Version] |
| SDK | [Version] |
| Region | [Region] |
| Language | [Languages tested] |
## Appendix
### Test Cases Executed
[Full list of test cases run]
### Evidence Archive
[Location of screenshots/videos]
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.
- 9d ago First seen · 181 lines · 12 tokens per session scan A 202f53f21141
compliance-audit is a command published in the GitHub repository sponticelli/gamedev-claude-plugins (15 stars, last pushed 8mo ago), licensed MIT. It adds 12 tokens to every session and 920 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-30.
Other commands, from other repositories
art-3d-pass
Review 3D art assets for export conventions, rigs, animation clips, materials, lighting, and LOD compliance.
cert-check
Review the current state against certification and platform compliance expectations.
asset-audit
Audit assets for compliance with standards.
accessibility-audit
You are an accessibility expert specializing in WCAG compliance, inclusive design, and assistive technology compatibility. Conduct comprehensive audits, identify barriers, provide remediation guidance, and ensure digital products are accessible to all users.
deps-audit
Audit project dependencies for vulnerabilities, outdated packages, license conflicts, and supply chain risks — then provide actionable remediation strategies.
review-epo-claims
Analyze patent claims for EPO Art. 84 EPC compliance - clarity, conciseness, support by description.