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-narrativegit 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-narrative)<a href="https://agentmods.dev/skills/googilyboogily/googilyboogily-claude-power-tools/audit-narrative"><img src="https://agentmods.dev/badge/skills/googilyboogily/googilyboogily-claude-power-tools/audit-narrative/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-narrative"><img src="https://agentmods.dev/badge/skills/googilyboogily/googilyboogily-claude-power-tools/audit-narrative.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.00042 | $0.01424 |
| Opus 5 | $0.00021 | $0.00712 |
| Sonnet 5 | $0.00008 | $0.00285 |
| Haiku 4.5 | $0.00004 | $0.00142 |
Grade A, and why
audit-narrative 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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Narrative Phase — Audit
Audit the Narrative phase (Phase 3) of a Game Design Bible for consistency with design pillars, systems designs, and project scope. Checks narrative weight appropriateness, character-gameplay integration, dialogue feasibility, and source integrity. 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/narrative-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 narrative weight.
- Read
<bible-dir>/DESIGN-PILLARS.md— the standard against which everything is measured. - Read all files in
<bible-dir>/03-narrative/using Glob. - Read all files in
<bible-dir>/02-systems/using Glob — needed for systems integration checks. - Read
<bible-dir>/01-core-loop/core-loop.md— needed for gameplay-narrative integration.
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 (e.g., voice acting checks for LIGHT narrative weight).
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 · 165 lines · 42 tokens per session scan A 84fa0d9603de
audit-narrative is a skill published in the GitHub repository GoogilyBoogily/googilyboogily-claude-power-tools (2 stars, last pushed 4mo ago), licensed MIT. It adds 42 tokens to every session and 1,424 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.