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-expandgit 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-expand)<a href="https://agentmods.dev/skills/googilyboogily/googilyboogily-claude-power-tools/bible-expand"><img src="https://agentmods.dev/badge/skills/googilyboogily/googilyboogily-claude-power-tools/bible-expand/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-expand"><img src="https://agentmods.dev/badge/skills/googilyboogily/googilyboogily-claude-power-tools/bible-expand.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.00029 | $0.01314 |
| Opus 5 | $0.00015 | $0.00657 |
| Sonnet 5 | $0.00006 | $0.00263 |
| Haiku 4.5 | $0.00003 | $0.00131 |
Grade A, and why
bible-expand 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bible Expand — Section Deep-Dive
Argument Parsing
Parse the following from $ARGUMENTS:
section-path: Path to a file or directory within the bible, relative to bible root (optional — prompt if missing)aspect: Specific aspect to explore, e.g., "economy balancing", "boss design", "environmental storytelling" (optional)
Step 1: Locate the Bible Root
If section-path is relative, resolve it by searching upward for INDEX.md to find the bible root.
If no section-path provided:
- Find the bible root (look for INDEX.md in current directory or parent directories)
- Read INDEX.md
- Present the section list:
"Which section would you like to expand?" [numbered list of all sections from INDEX.md with their current file sizes]
- Wait for user selection
Step 2: Re-establish Pillar Context
Read <bible-root>/DESIGN-PILLARS.md.
ALWAYS re-read pillars — every expansion must align with the established design pillars. This is non-negotiable.
Step 3: Read Target Section
Resolve the section path:
- If file: Read the target file
- If directory: Read all
.mdfiles in the directory, build a content map
Also read cross-referenced files:
- Grep the target for references to other bible sections (patterns like
see [section-name], links to other files) - Read referenced files to understand the full context
Present a section summary:
"📄 [Section Name]
- Current size: N lines
- Cross-references: [list]
- Open questions: [count]
- Pillar alignment: [which pillars this section serves]"
Step 4: Assess Expansion Type
Based on the section content and user's aspect request, determine the expansion type:
A. Depth Expansion
The section exists but needs more detail within its current structure.
- Trigger: Section is thin (< 50 lines of content), or user asks for "more detail"
- Action: Edit the existing file to add depth to existing subsections
B. Split Expansion
The section is too large or covers too many topics for a single file.
- Trigger: File exceeds 300 lines, or covers 3+ distinct topics
- Action: Create a subdirectory, split into focused sub-files, update the original as an index
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 · 142 lines · 29 tokens per session scan A 985a43b4b345
bible-expand is a skill published in the GitHub repository GoogilyBoogily/googilyboogily-claude-power-tools (2 stars, last pushed 4mo ago), licensed MIT. It adds 29 tokens to every session and 1,314 once invoked, about $0.0001 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.