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-to-hld-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/bible-to-hld-gather)<a href="https://agentmods.dev/skills/googilyboogily/googilyboogily-claude-power-tools/bible-to-hld-gather"><img src="https://agentmods.dev/badge/skills/googilyboogily/googilyboogily-claude-power-tools/bible-to-hld-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/bible-to-hld-gather"><img src="https://agentmods.dev/badge/skills/googilyboogily/googilyboogily-claude-power-tools/bible-to-hld-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.00040 | $0.02110 |
| Opus 5 | $0.00020 | $0.01055 |
| Sonnet 5 | $0.00008 | $0.00422 |
| Haiku 4.5 | $0.00004 | $0.00211 |
Grade A, and why
bible-to-hld-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 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 — 243 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bible-to-HLD — Context Gathering
Gather all context needed to generate game-development-aware High Level Design documents from a completed Game Design Bible. This skill runs an interactive session to load the bible, present a feature inventory for selection, gather technical context, dispatch research, and compile a structured context file that bible-to-hld-generate consumes.
Input
$ARGUMENTS — bible directory path and optional flags:
--features f1,f2,...— comma-separated feature names to skip interactive selection--codebase <path>— path to existing game codebase for technical context
Parse Arguments
Extract from $ARGUMENTS:
- Bible Directory: First non-flag argument (default:
docs/game-design-bible/) - Features:
--features f1,f2,...— comma-separated list (bypasses Phase 2 interactive selection) - Codebase Path:
--codebase <path>— path to existing game codebase
Source Integrity Rules
- Cite bible sources — every design claim in the context file must trace back to a specific bible section. If no source exists, flag it in Open Questions.
- Never invent game design details — if the bible doesn't specify something, leave it as an open question. HLDs translate design into architecture; they do not create new design.
- Technical context must come from Phase 3 — engine, platform, and codebase details come only from the Technical Landscape gathered in Phase 3, not from assumptions.
Phase 1: Load Bible Context
Step 1: Validate Bible Exists
Use Glob to check for <bible-dir>/INDEX.md. If it does not exist:
- Inform the user: "No Game Design Bible found at
<bible-dir>. Create one first with/game-design-bible:bible:create." - STOP
Step 2: Read Core Bible Files
Read these files — they provide the foundation for every HLD:
<bible-dir>/INDEX.md— check phase completion status<bible-dir>/DESIGN-PILLARS.md— the supreme court for all design decisions<bible-dir>/01-core-loop/core-loop.md— the fundamental gameplay loop
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 · 243 lines · 40 tokens per session scan A ed0cffa01a66
bible-to-hld-gather is a skill published in the GitHub repository GoogilyBoogily/googilyboogily-claude-power-tools (2 stars, last pushed 4mo ago), licensed MIT. It adds 40 tokens to every session and 2,110 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.