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 core-loop-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/core-loop-gather)<a href="https://agentmods.dev/skills/googilyboogily/googilyboogily-claude-power-tools/core-loop-gather"><img src="https://agentmods.dev/badge/skills/googilyboogily/googilyboogily-claude-power-tools/core-loop-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/core-loop-gather"><img src="https://agentmods.dev/badge/skills/googilyboogily/googilyboogily-claude-power-tools/core-loop-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.00047 | $0.01642 |
| Opus 5 | $0.00023 | $0.00821 |
| Sonnet 5 | $0.00009 | $0.00328 |
| Haiku 4.5 | $0.00005 | $0.00164 |
Grade A, and why
core-loop-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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Core Loop Context Gathering
Gather all context needed to write the Core Loop phase (Phase 1) of a Game Design Bible. This skill asks clarifying questions about the fundamental gameplay loop, explores prior concept work, dispatches parallel web research, and compiles everything into a structured context file that the core-loop-generate skill consumes.
Input
$ARGUMENTS
Parse Arguments
Extract from $ARGUMENTS:
- Bible Directory:
--bible-dir <path>(default:docs/game-design-bible/)
Source Integrity Rules
Every factual claim in the context file must be traceable to research performed in this session.
- Cite your work. When referencing design pillars, concept documents, or genre conventions, cite the specific file path and section that informed the claim.
- Never reference prior Claude sessions or Claude memory. Do not use phrases like "from our previous conversation," "as we discussed before," "based on prior analysis." Each context file stands on its own.
- Assumptions are labeled, not hidden. If you lack evidence for a claim, label it explicitly in the Open Questions section.
Process
Human-in-the-loop: Never proceed past a decision point without user approval.
Phase 1: Load Existing Context
- Validate
<bible-dir>/INDEX.mdexists. If not, inform the user: "No Game Design Bible found at<bible-dir>. Create one first with/game-design-bible:bible:create." — then STOP. - Read
<bible-dir>/DESIGN-PILLARS.md— extract all pillar names and their definitions. These constrain the entire core loop. - Read all files in
<bible-dir>/00-concept/— extract genre, platform, audience, vision, and non-goals.
CHECKPOINT — Confirm Foundation: Present what you found:
- Design pillars (name + one-line summary each)
- Genre, platform, and target audience from concept docs
- Any concept-level hints about gameplay (from vision or elevator pitch)
Ask: "Does this match your understanding? Anything I should know before we dig into the core 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 · 157 lines · 47 tokens per session scan A c803249e5092
core-loop-gather is a skill published in the GitHub repository GoogilyBoogily/googilyboogily-claude-power-tools (2 stars, last pushed 4mo ago), licensed MIT. It adds 47 tokens to every session and 1,642 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.