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-generategit 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-generate)<a href="https://agentmods.dev/skills/googilyboogily/googilyboogily-claude-power-tools/bible-to-hld-generate"><img src="https://agentmods.dev/badge/skills/googilyboogily/googilyboogily-claude-power-tools/bible-to-hld-generate/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-generate"><img src="https://agentmods.dev/badge/skills/googilyboogily/googilyboogily-claude-power-tools/bible-to-hld-generate.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.01505 |
| Opus 5 | $0.00020 | $0.00753 |
| Sonnet 5 | $0.00008 | $0.00301 |
| Haiku 4.5 | $0.00004 | $0.00151 |
Grade A, and why
bible-to-hld-generate 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 — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bible-to-HLD — Document Generator
Generate game-development-aware High Level Design documents from a previously gathered context file. Dispatches one game-hld-writer subagent per selected feature in parallel, then creates an INDEX.md with pillar coverage matrix and cross-reference summary.
Input
$ARGUMENTS — path to the context file (e.g., docs/game-design-bible/context/bible-to-hld-context.md)
Source Integrity Rules
- Cite bible sources — every design claim in an HLD 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 the context file — engine, platform, and codebase details come only from the Technical Landscape Summary, not from assumptions.
Process
Step 1: Read Context File
Read the context file from $ARGUMENTS. Extract:
- Selected Features: Feature names, bible source paths, pillar alignment, categories
- Technical Landscape Summary: Engine, platforms, multiplayer, constraints
- Design Pillars: All pillar names and descriptions
- Core Loop Summary: Fundamental gameplay loop
- Sibling Features: Full list with output paths for cross-referencing
- Output Directory: Where to write HLD documents (default:
docs/hld/) - Bible Directory: Source bible path
Step 2: Create Output Directory
mkdir -p <output-dir>
Step 3: Confirm Generation Plan
CHECKPOINT — Confirm Generation Plan
Present the full generation plan:
## Generation Plan
| # | Feature | Bible Source | Output Path |
|---|---------|-------------|-------------|
| 1 | [feature name] | [bible-dir]/[path] | <output-dir>/hld-[slug].md |
| 2 | ... | ... | ... |
**Engine:** [from context]
**Platforms:** [from context]
**Total HLDs to generate:** [count]
Proceed with generation? (y/n)
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 · 171 lines · 40 tokens per session scan A 9b7b991226c8
bible-to-hld-generate 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 1,505 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.