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-pipelinegit 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-pipeline)<a href="https://agentmods.dev/skills/googilyboogily/googilyboogily-claude-power-tools/bible-to-hld-pipeline"><img src="https://agentmods.dev/badge/skills/googilyboogily/googilyboogily-claude-power-tools/bible-to-hld-pipeline/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-pipeline"><img src="https://agentmods.dev/badge/skills/googilyboogily/googilyboogily-claude-power-tools/bible-to-hld-pipeline.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.00043 | $0.01009 |
| Opus 5 | $0.00022 | $0.00504 |
| Sonnet 5 | $0.00009 | $0.00202 |
| Haiku 4.5 | $0.00004 | $0.00101 |
Grade A, and why
bible-to-hld-pipeline 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bible-to-HLD — Full Pipeline
Run the complete Bible-to-HLD pipeline end-to-end: gather context from a completed Game Design Bible, dispatch parallel HLD generation with one agent per feature, then audit all generated HLDs for quality and consistency. Each phase runs with clean context isolation.
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 interactive selection in gather phase) - Codebase Path:
--codebase <path>— path to existing game codebase
Phase 1: Gather Context
Invoke the gather skill to load the bible, present feature inventory, gather technical context, and compile a context file.
Skill(bible-to-hld-gather, "<bible-dir> [--features <features>] [--codebase <codebase>]")
Capture the returned context file path as $CONTEXT_PATH.
CHECKPOINT — Review Context & Feature Selection
Read the context file at $CONTEXT_PATH and present a summary:
## Pipeline Phase 1 Complete: Context Gathered
**Context file:** [path]
**Selected features:** [count]
**Technical landscape:** [engine, platforms summary]
| # | Feature | Bible Source | Category |
|---|---------|-------------|----------|
| 1 | [name] | [path] | [category] |
| ... | ... | ... | ... |
Proceed to HLD generation? (y/n/edit context)
- If "edit context": Inform the user to edit the context file manually, then re-read and re-present.
- If "n": STOP.
- If "y": Proceed to Phase 2.
Phase 2: Generate HLDs
Invoke the generate skill to dispatch parallel HLD writers and create INDEX.md.
Skill(bible-to-hld-generate, "$CONTEXT_PATH")
Capture the returned HLD directory as $HLD_DIR.
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 · 143 lines · 43 tokens per session scan A 6727e9fd4c45
bible-to-hld-pipeline is a skill published in the GitHub repository GoogilyBoogily/googilyboogily-claude-power-tools (2 stars, last pushed 4mo ago), licensed MIT. It adds 43 tokens to every session and 1,009 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.