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/build-audit)<a href="https://agentmods.dev/commands/sponticelli/gamedev-claude-plugins/build-audit"><img src="https://agentmods.dev/badge/commands/sponticelli/gamedev-claude-plugins/build-audit.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.00010 | $0.00727 |
| Opus 5 | $0.00005 | $0.00364 |
| Sonnet 5 | $0.00002 | $0.00145 |
| Haiku 4.5 | $0.00001 | $0.00073 |
Grade A, and why
build-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 8d 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build System Audit
Analyze the current build configuration and identify optimization opportunities.
Context Gathering
Before auditing, understand:
Build Environment
- Engine and version
- Build system (MSBuild, Gradle, SCons, etc.)
- Current build times (full and incremental)
- Hardware specs (CPU, RAM, storage type)
Known Issues
- Slowest build stages
- Frequent rebuild triggers
- Cache effectiveness
- Error patterns
Audit Checklist
Configuration
- Parallel jobs configured appropriately
- Incremental builds enabled
- Unnecessary features disabled
- Compiler optimizations appropriate for stage
Caching
- Build cache enabled and effective
- Cache hits vs misses tracked
- Cache size appropriate
- Cache invalidation working correctly
Dependencies
- Dependencies are properly declared
- No circular dependencies
- Version pinning consistent
- Unused dependencies removed
Assets
- Asset import settings optimized
- Texture compression appropriate
- Audio formats optimized
- Unnecessary assets excluded
Output Format
# Build Audit Report: [Project Name]
## Executive Summary
**Current Full Build:** [Time]
**Current Incremental:** [Time]
**Primary Bottleneck:** [Stage/Component]
**Estimated Improvement:** [%]
## Build Profile
### Time Breakdown
| Stage | Duration | % Total | Notes |
|-------|----------|---------|-------|
| Compilation | [Time] | [%] | [Observation] |
| Asset processing | [Time] | [%] | [Observation] |
| Linking | [Time] | [%] | [Observation] |
| Packaging | [Time] | [%] | [Observation] |
### Resource Usage
| Resource | Peak | Average | Bottleneck? |
|----------|------|---------|-------------|
| CPU | [%] | [%] | [Yes/No] |
| Memory | [GB] | [GB] | [Yes/No] |
| Disk I/O | [MB/s] | [MB/s] | [Yes/No] |
## Findings
### Quick Wins (Implement Today)
| Finding | Current | Recommended | Expected Impact |
|---------|---------|-------------|-----------------|
| [Issue] | [State] | [Fix] | [Time saved] |
### Medium Effort (This Sprint)
| Finding | Current | Recommended | Expected Impact |
|---------|---------|-------------|-----------------|
| [Issue] | [State] | [Fix] | [Time saved] |
### Long-term (Requires Planning)
| Finding | Current | Recommended | Expected Impact |
|---------|---------|-------------|-----------------|
| [Issue] | [State] | [Fix] | [Time saved] |
## Cache Analysis
**Hit Rate:** [%]
**Recommendations:**
- [Cache improvement 1]
- [Cache improvement 2]
## Recommendations Summary
### Priority Order
1. [Highest impact optimization]
2. [Second priority]
3. [Third priority]
### Expected Results
| Phase | Time Reduction | Effort |
|-------|----------------|--------|
| Quick Wins | [%] | [Hours] |
| Medium Effort | [%] | [Days] |
| Long-term | [%] | [Weeks] |
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.
- 8d ago First seen · 119 lines · 10 tokens per session scan A 99e8df7bf51d
build-audit is a command published in the GitHub repository sponticelli/gamedev-claude-plugins (15 stars, last pushed 7mo ago), licensed MIT. It adds 10 tokens to every session and 727 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.