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-systemsgit 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-systems)<a href="https://agentmods.dev/skills/googilyboogily/googilyboogily-claude-power-tools/audit-systems"><img src="https://agentmods.dev/badge/skills/googilyboogily/googilyboogily-claude-power-tools/audit-systems/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-systems"><img src="https://agentmods.dev/badge/skills/googilyboogily/googilyboogily-claude-power-tools/audit-systems.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.01577 |
| Opus 5 | $0.00022 | $0.00788 |
| Sonnet 5 | $0.00009 | $0.00315 |
| Haiku 4.5 | $0.00004 | $0.00158 |
Grade A, and why
audit-systems 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 — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Systems Phase — Audit
Audit all Phase 2 (Systems) documents for quality, completeness, pillar alignment, cross-system consistency, and design integrity. 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 — path to the bible directory, and optionally:
--context <path>— context file from the gather phase (enables context fidelity checks)
Parse Arguments
Extract from $ARGUMENTS:
- Bible Directory: First non-flag argument (default:
docs/game-design-bible/) - Context File Path:
--context <path>(optional)
Process
Phase 1: Load Documents
-
Read
<bible-dir>/INDEX.md— verify Phase 2 is✅ Complete. If not, warn: "Phase 2 is not marked complete. Auditing incomplete systems may produce misleading results. Continue anyway?" Wait for confirmation. -
Read
<bible-dir>/DESIGN-PILLARS.md— extract all pillar names and "What This Rules Out" lists. -
Read
<bible-dir>/01-core-loop/core-loop.md— extract the core loop cycle. -
Use Glob to find all
.mdfiles in<bible-dir>/02-systems/. Read each one. -
If
--contextprovided, read the context file. -
Read the audit checklist at
${CLAUDE_SKILL_DIR}/references/checklist.md.
Phase 2: Run All Checks
Run every check from the checklist against every system document. Build a prioritized issue queue:
- 🔴 CRITICAL issues first
- 🟡 WARNING issues next
- 🔵 INFO issues last
Per-system checks (SC, PA categories): Run against each individual system document.
Cross-system checks (CS category): Run across all system documents together — look for conflicts, inconsistencies, and missing cross-references.
Core loop checks (CL category): Verify each system connects to the core loop without bypassing it.
Source integrity checks (SI category): Scan all documents for prior-session references and unlabeled assumptions.
Context fidelity checks (CF category): Only run if --context was provided. Compare documents against the gather-phase context file.
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 · 198 lines · 43 tokens per session scan A 98aafb52a879
audit-systems 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,577 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
minecraft-debug-mcp
Operate and debug the live Minecraft bot through its built-in MCP REPL server. Use when work requires starting the bot with pnpm dev, connecting to the local MCP endpoint, inspecting cognitive state/logs/history, injecting synthetic chat/events, or running targeted REPL code against the running brain during…
graphics-api-hooking
Analyze Direct3D/DXGI, OpenGL, and Vulkan rendering, presentation, composition, and capture evidence. Use to distinguish API samples, PresentMon event metrics, Tracy instrumentation, compatibility translation, frame images, and validation diagnostics; review swap chains, overlays, resource lifetime, and…
console-get-logs
Retrieve Unity Editor logs from the MCP plugin's LogCollector, optionally filtered by log type or time window. Useful for debugging and monitoring Editor activity.
editor-application-get-state
Return the current state of UnityEditor.EditorApplication — playmode, paused state, compilation state, and related flags.
console-clear-logs
Clear the MCP log cache (used by 'console-get-logs') and the Unity Editor Console window. Useful for isolating logs to a specific action by clearing the slate first.
profiler-start
Enable Unity's runtime profiler and open the Profiler window. Idempotent: calling when already enabled returns the current enabled state without error.