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 bible-reviewgit 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/bible-review)<a href="https://agentmods.dev/skills/googilyboogily/googilyboogily-claude-power-tools/bible-review"><img src="https://agentmods.dev/badge/skills/googilyboogily/googilyboogily-claude-power-tools/bible-review/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/bible-review"><img src="https://agentmods.dev/badge/skills/googilyboogily/googilyboogily-claude-power-tools/bible-review.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.00056 | $0.02117 |
| Opus 5 | $0.00028 | $0.01059 |
| Sonnet 5 | $0.00011 | $0.00423 |
| Haiku 4.5 | $0.00006 | $0.00212 |
Grade A, and why
bible-review 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 — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bible Review — Cross-Cutting Audit
Argument Parsing
Parse the following from $ARGUMENTS:
bible-dir: Path to the Game Design Bible root directory (required — prompt if missing)--focus: Audit focus area — one ofall(default),pillars,systems,narrative,scope--quick: Skip interactive briefing (Step 0) and synthesis (Step 5), run audits and present findings only
Step 0: Pre-Review Briefing (skip if --quick)
Read <bible-dir>/INDEX.md and <bible-dir>/DESIGN-PILLARS.md.
Present the bible health snapshot:
- Total file count (Glob
**/*.md) - Phases completed vs incomplete (from INDEX.md status markers)
- Pillar list with one-line summaries
- Open questions count (Grep for
> **Open Questionor❓across all files)
Ask the user:
- "Any specific concerns or areas you want me to focus on?"
- "Any known issues I should ignore during this audit?"
Record responses as audit context.
Step 1: Pillar Consistency Audit
Dispatch the game-design-reviewer agent with the following task:
Audit Type: Pillar Consistency Bible Directory:
<bible-dir>Instructions: Read DESIGN-PILLARS.md and every section file. For each feature/system, verify it serves at least one pillar. For each pillar, verify at least one feature serves it. Flag any feature that contradicts a pillar's "What This Rules Out" list. Check that DESIGN-PILLARS.md matches 00-concept/design-pillars.md. Verify MDA aesthetics align with the pillar set. Output: Write findings to<bible-dir>/reviews/pillar-consistency.mdusing severity markers: 🔴 Critical, 🟡 Warning, 🔵 Info, ❓ Needs Clarification.
Wait for this audit to complete before proceeding — its results feed into Step 2.
Step 2: Contradictions + Pitfall Detection (Parallel)
Read the pillar consistency results from <bible-dir>/reviews/pillar-consistency.md.
Dispatch 2 parallel Tasks:
Task 1: Internal Contradictions
Dispatch game-design-reviewer agent:
Audit Type: Internal Contradictions Bible Directory:
<bible-dir>Pillar Audit Context: [include pillar consistency findings] Check Categories:
- Systems vs Systems: conflicting mechanics, overlapping resource economies, contradictory progression curves
- Systems vs Narrative: mechanics that undermine story themes, narrative promises mechanics can't deliver
- Art/Audio vs Tone: visual style mismatches with stated tone, audio direction contradicting atmosphere goals
- Terminology: same concept with different names across files, or same name meaning different things
- Numeric Conflicts: contradictory stats, values that don't add up, percentage allocations exceeding 100% Output: Write to
<bible-dir>/reviews/contradictions.mdwith severity markers.
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 · 209 lines · 56 tokens per session scan A edf6fa30e028
bible-review is a skill published in the GitHub repository GoogilyBoogily/googilyboogily-claude-power-tools (2 stars, last pushed 4mo ago), licensed MIT. It adds 56 tokens to every session and 2,117 once invoked, about $0.0003 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.