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 GoogilyBoogily/googilyboogily-claude-power-tools --skill audit-technicalgit clone --depth 1 https://github.com/GoogilyBoogily/googilyboogily-claude-power-toolsWrote 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/googilyboogily/googilyboogily-claude-power-tools/audit-technical)<a href="https://agentmods.dev/skills/googilyboogily/googilyboogily-claude-power-tools/audit-technical"><img src="https://agentmods.dev/badge/skills/googilyboogily/googilyboogily-claude-power-tools/audit-technical/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/skills/googilyboogily/googilyboogily-claude-power-tools/audit-technical"><img src="https://agentmods.dev/badge/skills/googilyboogily/googilyboogily-claude-power-tools/audit-technical.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.00035 | $0.02262 |
| Opus 5 | $0.00017 | $0.01131 |
| Sonnet 5 | $0.00007 | $0.00452 |
| Haiku 4.5 | $0.00003 | $0.00226 |
Grade A, and why
audit-technical 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 — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Technical & Production Audit
Audit the Technical & Production phase (Phase 5) of a Game Design Bible for engine justification, timeline realism, scope/resource alignment, monetization ethics, and document completeness. Findings are written to an audit report with interactive resolution.
Input
$ARGUMENTS
Parse Arguments
Extract from $ARGUMENTS:
- Bible Directory: First non-flag argument (default:
docs/game-design-bible/) - Context File:
--context <path>(optional — enables Context Fidelity checks)
Source Integrity Rules
The audit itself must not introduce ungrounded claims.
- Cite what you check. Reference specific file paths, section names, and line content when reporting findings.
- Never reference prior Claude sessions or Claude memory.
- Distinguish fact from judgment. Findings are grounded in the checklist; recommendations are clearly labeled as such.
Process
Step 1: Load Documents
- Read
<bible-dir>/DESIGN-PILLARS.md - Read all files in
<bible-dir>/05-technical-production/:engine-and-tools.mdasset-breakdown.mdtimeline.mdmonetization.md(may not exist — check first)
- Scan prior phase directories for scope comparison:
<bible-dir>/00-concept/<bible-dir>/01-core-loop/<bible-dir>/02-systems/<bible-dir>/03-narrative/<bible-dir>/04-art-audio/
- If
--contextwas provided, read the context file.
Step 2: Load Checklist
Read the checklist from ${CLAUDE_SKILL_DIR}/references/checklist.md.
Step 3: Run Checklist
Evaluate every check item against the loaded documents. For each item, determine:
- ✅ PASS — requirement is met with evidence
- ❌ FAIL — requirement is not met, cite what's missing or wrong
- ⚠️ PARTIAL — partially met, explain the gap
- ⏭️ SKIP — not applicable (e.g., Context Fidelity checks when no
--contextprovided, monetization ethics when no monetization file)
Special attention areas:
What ships with it
1 file 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.
- 9d ago First seen · 200 lines · 35 tokens per session scan A 4e2a8cb09f72
audit-technical is a skill published in the GitHub repository GoogilyBoogily/googilyboogily-claude-power-tools (2 stars, last pushed 4mo ago), licensed MIT. It adds 35 tokens to every session and 2,262 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-09-03.
Other skills, from other repositories
gameobject-component-destroy
Destroy one or more Components from a target GameObject. Missing (null) components are skipped — they cannot be destroyed. Use 'gameobject-find' and 'gameobject-component-get' to identify the components first.
unity-version-split
Split a C# file into Unity 6.5+ and pre-Unity 6.5 variants. Use when a file needs different implementations for different Unity versions due to API changes (e.g., EntityId vs int, GetEntityId vs GetInstanceID).
godot-signals-groups
Build event-driven, decoupled Godot 4.7 gameplay with signals and node groups: declare and emit custom signals, connect with Callables (incl. bind/one-shot), and broadcast to many nodes via groups and callgroup. Use when wiring node communication in a Godot project, replacing tight references with signals…
motion
How an agent turns a character mesh into a usable animated FBX — and how to judge whether the result is shippable.
unity-addressables
Manage Addressables groups, entries, profiles and content builds (com.unity.addressables, reflection-based).
threejs-exposure-color-grading
Build a measured exposure and grading path in Three.js. Use for a 64x36 encoded luminance meter, asynchronous readback, weighted log-average exposure, asymmetric adaptation, single tone-map ownership, and a generated 32-cube post-tone-map LUT.