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 systems-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/systems-generate)<a href="https://agentmods.dev/skills/googilyboogily/googilyboogily-claude-power-tools/systems-generate"><img src="https://agentmods.dev/badge/skills/googilyboogily/googilyboogily-claude-power-tools/systems-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/systems-generate"><img src="https://agentmods.dev/badge/skills/googilyboogily/googilyboogily-claude-power-tools/systems-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.00035 | $0.01526 |
| Opus 5 | $0.00017 | $0.00763 |
| Sonnet 5 | $0.00007 | $0.00305 |
| Haiku 4.5 | $0.00003 | $0.00153 |
Grade A, and why
systems-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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Systems Phase — Document Generation
Generate all Phase 2 (Systems) documents by dispatching parallel systems-designer subagents. Each agent receives focused context for one system and writes a complete design document. This skill runs with clean context — all questions were answered during the gather phase.
Input
$ARGUMENTS — path to the context file (e.g., docs/game-design-bible/context/systems-context.md), and optionally --output-dir <path>.
Parse Arguments
Extract from $ARGUMENTS:
- Context File: First non-flag argument
- Output Directory:
--output-dir <path>(default: derived from context file'sBible Directoryfield)
Source Integrity Rules
Every design decision must trace back to the context file.
- Ground every claim. Every factual statement must trace back to a specific entry in the context file (user answers, pillar context, core loop context, or web research with URLs).
- Flag ungrounded claims. If a subagent needs to state something not in the context file, it must mark it as
[ASSUMPTION]. - Never invent game design details. If the context file doesn't cover something, put it in Open Questions — don't fabricate.
Process
Step 1: Read and Validate Context
-
Read the context file from
$ARGUMENTS. -
Extract:
- Selected Systems — the numbered list of systems to design
- Per-System Details — questions, answers, and research findings for each system
- Bible Directory — path to the bible root
- Scope — indie/aa/aaa
- Design Pillars — pillar names and "What This Rules Out" lists
- Core Loop — the Action → Feedback → Reward → Motivation cycle
- Genre & Platform — from vision context
- Cross-System Considerations — shared resources, dependencies
-
Validate:
- At least one system is selected
- Per-system details exist for every selected system
- Bible directory path is valid
-
Derive paths:
- Pillars Path:
<bible-dir>/DESIGN-PILLARS.md - Core Loop Path:
<bible-dir>/01-core-loop/core-loop.md - Output Directory:
<output-dir>or<bible-dir>/02-systems/
- Pillars Path:
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 · 160 lines · 35 tokens per session scan A 05a756e06c7d
systems-generate is a skill published in the GitHub repository GoogilyBoogily/googilyboogily-claude-power-tools (2 stars, last pushed 4mo ago), licensed MIT. It adds 35 tokens to every session and 1,526 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.