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 art-audio-generategit 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/art-audio-generate)<a href="https://agentmods.dev/skills/googilyboogily/googilyboogily-claude-power-tools/art-audio-generate"><img src="https://agentmods.dev/badge/skills/googilyboogily/googilyboogily-claude-power-tools/art-audio-generate/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/art-audio-generate"><img src="https://agentmods.dev/badge/skills/googilyboogily/googilyboogily-claude-power-tools/art-audio-generate.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.00049 | $0.02828 |
| Opus 5.5 | $0.00020 | $0.01131 |
| Sonnet 5.5 | $0.00010 | $0.00566 |
| Haiku 4.5 | $0.00005 | $0.00283 |
Grade A, and why
art-audio-generate 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 1mo 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 — 253 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Art & Audio Phase — Document Generator
Generate the complete Art & Audio phase (Phase 4) of a Game Design Bible from a previously gathered context file. This skill runs with clean context and is non-interactive — all questions were answered during the gather phase. Dispatches the art-audio-director agent to produce all five documents.
Input
$ARGUMENTS — path to the context file (e.g., docs/game-design-bible/context/art-audio-context.md), and optionally:
--output-dir <path>— override the output directory from the context file
Parse Arguments
Extract from $ARGUMENTS:
- Context File: First non-flag argument
- Output Dir:
--output-dir <path>, or extracted from the context file'sBible Directoryfield
Source Integrity Rules
Every factual claim in these documents must be traceable to the context file.
- Ground every claim. Every statement must trace back to the context file — user answers, research findings with URLs, or design pillar deliberations.
- Flag ungrounded claims. If you need to state something not in the context file, mark it explicitly as
[ASSUMPTION]. - Never invent details. If the context file doesn't cover something, put it in Open Questions — don't fabricate.
Process
Step 1: Read Inputs
- Read the context file from
$ARGUMENTS. - Extract all gathered information:
- Visual references, art style, visual mood
- Audio mood, adaptive audio, silence strategy, SFX philosophy
- UI philosophy (HUD, menus, information density)
- Controls preferences (input feel, platform needs)
- Accessibility priorities (which of 6 categories, depth)
- MDA context (target aesthetics)
- Pillar context (design pillars and how art/audio serves them)
- Scope tier (indie / aa / aaa)
- Web research findings
- Open questions
- Output directory
Step 2: Create Directory Structure
mkdir -p <output-dir>/04-art-audio
Step 3: Dispatch Art-Audio Director Agent
Dispatch the art-audio-director agent via Task with the full context. The agent must NOT ask questions — all context has been gathered.
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.
- 1mo ago First seen · 253 lines · 49 tokens per session scan A eba0611f84e6
art-audio-generate is a skill published in the GitHub repository GoogilyBoogily/googilyboogily-claude-power-tools (2 stars, last pushed 5mo ago), licensed MIT. It adds 49 tokens to every session and 2,828 once invoked, about $0.0002 per session on Opus 5.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
ux-review
Validate a UX spec, HUD design or pattern library — accessibility, GDD alignment, readiness. APPROVED / NOT ASSESSED / NEEDS REVISION / MAJOR REVISION NEEDED.
ux-design
Section-by-section UX spec authoring for a screen, flow or HUD. Reads the player journey to provide context; also project-wide accessibility.
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…
unity-inspector
Advise on Unity Inspector authoring UX.
scenario-roblox-ui
Use when building or fixing Roblox game UI or input: HUD (health bar, currency, ability cooldowns), main menu, shop with a scrolling grid, settings screen, inventory, "UI scales wrong on phone", buttons hidden behind the jump button, UI too small on a tablet or TV, portrait and landscape, top bar and safe area, Scale…