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-art-audiogit 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-art-audio)<a href="https://agentmods.dev/skills/googilyboogily/googilyboogily-claude-power-tools/audit-art-audio"><img src="https://agentmods.dev/badge/skills/googilyboogily/googilyboogily-claude-power-tools/audit-art-audio/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-art-audio"><img src="https://agentmods.dev/badge/skills/googilyboogily/googilyboogily-claude-power-tools/audit-art-audio.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.00036 | $0.01397 |
| Opus 5 | $0.00018 | $0.00698 |
| Sonnet 5 | $0.00007 | $0.00279 |
| Haiku 4.5 | $0.00004 | $0.00140 |
Grade A, and why
audit-art-audio 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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Art & Audio Phase — Audit
Audit the Art & Audio phase (Phase 4) of a Game Design Bible for style consistency, pillar alignment, accessibility completeness, and scope feasibility. Produces a structured audit report with interactive resolution of findings.
Input
$ARGUMENTS
Parse Arguments
Extract from $ARGUMENTS:
- Bible Directory: First non-flag argument (default:
docs/game-design-bible/) - Context File:
--context <path>(default:<bible-dir>/context/art-audio-context.md)
Source Integrity Rules
The audit itself must be grounded in evidence from the documents being audited.
- Cite every finding. Reference specific file paths, section headers, and quoted text when flagging an issue.
- Never reference prior Claude sessions or Claude memory.
- Distinguish facts from opinions. Objective issues (contradictions, missing sections) are findings. Subjective preferences are suggestions.
Process
Step 1: Load Documents
- Validate
<bible-dir>/INDEX.mdexists. If not, STOP with an error message. - Read the context file (if provided) to understand the original intent and user preferences.
- Read
<bible-dir>/DESIGN-PILLARS.md— the standard against which everything is measured. - Read all files in
<bible-dir>/04-art-audio/using Glob. - Read
<bible-dir>/00-concept/vision.md— for genre, platform, and audience context. - Read
<bible-dir>/00-concept/mda-analysis.md— for target aesthetics that art/audio should serve.
Step 2: Load Checklist
Read the audit checklist from ${CLAUDE_SKILL_DIR}/references/checklist.md.
Step 3: Run Checklist
Evaluate every item in the checklist against the loaded documents. For each item:
- ✅ PASS — Requirement is met. Note the evidence (file + section).
- ⚠️ WARN — Partially met or needs attention. Note what's missing.
- ❌ FAIL — Requirement not met. Note the specific gap.
- ⏭️ SKIP — Not applicable for this game's scope or platform.
Track severity from the checklist:
- 🔴 Critical — Must fix before proceeding to next phase
- 🟡 Important — Should fix, may cause problems downstream
- 🔵 Nice-to-have — Improvement opportunity, not blocking
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 · 163 lines · 36 tokens per session scan A 10e7867afa1e
audit-art-audio is a skill published in the GitHub repository GoogilyBoogily/googilyboogily-claude-power-tools (2 stars, last pushed 4mo ago), licensed MIT. It adds 36 tokens to every session and 1,397 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
roblox-ui
Build production Roblox interfaces with ScreenGui/PlayerGui lifecycle, responsive UDim2 layouts, safe insets, reusable editable Instances, cross-device input and selection, restrained motion, cleanup, and multi-viewport verification. Use for Roblox HUDs, inventories, shops, settings, ability bars, ScrollingFrames…
game-ui-ux
Design and build game UI/UX — HUDs, menus, and overlays — that survive every screen: anchor- based responsive layout, resolution/aspect scaling and safe areas, keyboard/gamepad focus navigation, a screen/menu state stack, and event-driven (not polled) HUD updates. Engine- neutral patterns that pair with the detected…
ux-design
Guided, section-by-section UX spec authoring for a screen, flow, or HUD. Reads game concept, player journey, and relevant GDDs to provide context-aware design guidance. Produces ux-spec.md (per screen/flow) or hud-design.md using the studio templates.
ux-review
Validates a UX spec, HUD design, or interaction pattern library for completeness, accessibility compliance, GDD alignment, and implementation readiness. Produces APPROVED / NEEDS REVISION / MAJOR REVISION NEEDED verdict with specific gaps.
unity-inspector
Advise on Unity Inspector authoring UX.
threejs-game-ui-designer
Design premium Three.js game UI: HUDs, menus, overlays, pause/win/lose screens, settings, icon controls, touch UI, typography, responsive layout, safe areas, text fit, and UI/world cohesion.