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-gathergit 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-gather)<a href="https://agentmods.dev/skills/googilyboogily/googilyboogily-claude-power-tools/art-audio-gather"><img src="https://agentmods.dev/badge/skills/googilyboogily/googilyboogily-claude-power-tools/art-audio-gather/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-gather"><img src="https://agentmods.dev/badge/skills/googilyboogily/googilyboogily-claude-power-tools/art-audio-gather.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.00050 | $0.02222 |
| Opus 5.5 | $0.00020 | $0.00889 |
| Sonnet 5.5 | $0.00010 | $0.00444 |
| Haiku 4.5 | $0.00005 | $0.00222 |
Grade A, and why
art-audio-gather 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 — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Art & Audio Phase — Context Gathering
Gather all context needed to write the Art & Audio phase (Phase 4) of a Game Design Bible. This skill runs an interactive Q&A session about visual style, audio direction, UI/UX philosophy, controls, and accessibility. It dispatches parallel research and compiles a structured context file that the art-audio-generate skill consumes.
Input
$ARGUMENTS
Parse Arguments
Extract from $ARGUMENTS:
- Bible Directory:
--bible-dir <path>(default:docs/game-design-bible/)
Source Integrity Rules
Every factual claim in the context file must be traceable to research performed in this session.
- Cite your work. When referencing design pillars, concept documents, or art/audio conventions, cite the specific file path and section that informed the claim.
- Never reference prior Claude sessions or Claude memory. Do not use phrases like "from our previous conversation," "as we discussed before," "based on prior analysis." Each context file stands on its own.
- Assumptions are labeled, not hidden. If you lack evidence for a claim, label it explicitly in the Open Questions section.
Process
Human-in-the-loop: Never proceed past a decision point without user approval.
Phase 1: Load Existing Context
Phase 4 depends primarily on Phase 0 (Concept) for tone, genre, and pillars.
- Validate
<bible-dir>/INDEX.mdexists. If not, inform the user: "No Game Design Bible found at<bible-dir>. Create one first with/game-design-bible:concept-gather." — then STOP. - Read
<bible-dir>/DESIGN-PILLARS.md— extract all pillar names and their definitions. - Read
<bible-dir>/00-concept/mda-analysis.md— extract target aesthetics (these directly inform art and audio direction). - Read
<bible-dir>/00-concept/vision.md— extract genre, platform, audience, and core fantasy.
CHECKPOINT — Confirm Foundation: Present what you found:
- Design pillars (name + one-line summary each)
- Target aesthetics from MDA analysis
- Genre, platform, and target audience
- Core fantasy and emotional tone
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 · 200 lines · 50 tokens per session scan A 43df5891850a
art-audio-gather is a skill published in the GitHub repository GoogilyBoogily/googilyboogily-claude-power-tools (2 stars, last pushed 5mo ago), licensed MIT. It adds 50 tokens to every session and 2,222 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…