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 audit-core-loopgit 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/audit-core-loop)<a href="https://agentmods.dev/skills/googilyboogily/googilyboogily-claude-power-tools/audit-core-loop"><img src="https://agentmods.dev/badge/skills/googilyboogily/googilyboogily-claude-power-tools/audit-core-loop/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/audit-core-loop"><img src="https://agentmods.dev/badge/skills/googilyboogily/googilyboogily-claude-power-tools/audit-core-loop.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.01637 |
| Opus 5.5 | $0.00016 | $0.00655 |
| Sonnet 5.5 | $0.00008 | $0.00327 |
| Haiku 4.5 | $0.00004 | $0.00164 |
Grade A, and why
audit-core-loop 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 1mo 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 — 206 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Core Loop Audit
Audit the Core Loop phase (Phase 1) of a Game Design Bible for quality, completeness, and correctness. Each issue is presented to the user one at a time with multiple resolution options, always including a research option that forks parallel web research agents.
Input
$ARGUMENTS
Parse Arguments
Extract from $ARGUMENTS:
- Bible Directory: First non-flag argument (default:
docs/game-design-bible/) - Context File Path:
--context <path>(optional, enables context fidelity checks)
Process
Phase 1: Load Documents
- Read
<bible-dir>/01-core-loop/core-loop.md. - Read
<bible-dir>/01-core-loop/prototype-spec.md. - Read
<bible-dir>/DESIGN-PILLARS.md— extract all pillar names. - If
--contextprovided, read the context file. - Read the audit checklist at
${CLAUDE_SKILL_DIR}/references/checklist.md.
If core-loop.md does not exist, inform the user: "No core loop documents found at <bible-dir>/01-core-loop/. Generate them first with /game-design-bible:core-loop-generate." — then STOP.
Phase 2: Run All Checks
Run every check from the checklist against the core loop documents. For each check, record:
- Check name and category
- Status: PASS, WARN, or FAIL
- Details: What was found (or not found)
- Severity: 🔴 CRITICAL, 🟡 WARNING, or 🔵 INFO
- Suggested fix: How to resolve
Also scan for open questions: TODO, TBD, FIXME, [ASSUMPTION], vague/placeholder text, or any unresolved items.
Build a prioritized issue queue ordered:
- 🔴 CRITICAL issues first
- 🟡 WARNING issues next
- 🔵 INFO issues last
- ❓ Open Questions last
Phase 3: Present Summary
Show the user the full breakdown before diving in:
## Core Loop Audit Summary: [Game Name]
**Bible Directory:** [bible-dir]
**Context file:** [path or "not provided"]
Found **N issues** and **M open questions**:
- 🔴 CRITICAL: [count] — must fix before proceeding
- 🟡 WARNING: [count] — should fix
- 🔵 INFO: [count] — optional improvements
- ❓ Open Questions: [count]
Starting sequential resolution...
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.
- 1mo ago First seen · 206 lines · 40 tokens per session scan A beba951bb4b6
audit-core-loop is a skill published in the GitHub repository GoogilyBoogily/googilyboogily-claude-power-tools (2 stars, last pushed 5mo ago), licensed MIT. It adds 40 tokens to every session and 1,637 once invoked, about $0.0002 per session on Opus 5.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
regression-suite
Map test coverage to GDD critical paths, find fixed bugs lacking regression tests, flag drift from new features.
soak-test
Soak test protocol for extended play — what to observe and log for slow leaks, fatigue, late-appearing edge cases.
playtest-report
Structured playtest report template, or turn existing playtest notes into structured feedback.
team-polish
Orchestrate the polish team — performance-analyst, technical-artist, sound-designer, qa-tester — to optimize and harden a feature or area.
smoke-check
Critical-path smoke gate before QA hand-off — runs the automated suite. A failed check means the build is not QA-ready.
develop-web-game
Use when Codex is building or iterating on a web game (HTML/JS) and needs a reliable development + testing loop: implement small changes, run a Playwright-based test script with short input bursts and intentional pauses, inspect screenshots/text, and review console errors with rendergametotext.