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 design-pillarsgit 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/design-pillars)<a href="https://agentmods.dev/skills/googilyboogily/googilyboogily-claude-power-tools/design-pillars"><img src="https://agentmods.dev/badge/skills/googilyboogily/googilyboogily-claude-power-tools/design-pillars/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/design-pillars"><img src="https://agentmods.dev/badge/skills/googilyboogily/googilyboogily-claude-power-tools/design-pillars.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.00055 | $0.01607 |
| Opus 5 | $0.00028 | $0.00804 |
| Sonnet 5 | $0.00011 | $0.00321 |
| Haiku 4.5 | $0.00006 | $0.00161 |
Grade A, and why
design-pillars 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Pillars Reference
Design pillars are the 3-5 non-negotiable principles that every feature, system, and piece of content must serve. They are the supreme court of design decisions — when two good ideas conflict, pillars break the tie.
The Power of Counterexamples
A pillar that says "Crafting creates strategy" is abstract. A pillar that says "This rules out: abundant ammo, auto-crafting, single optimal builds" is instantly understood. People grasp boundaries faster than descriptions — your brain builds a sharper mental model from "here's what we're NOT doing" than from "here's what we're doing."
When communicating pillars to a team, lead with what each pillar rules out. If someone reads only the counterexamples, they should already understand the design intent.
What Makes a Good Pillar
A strong design pillar is:
- Defined by exclusion: You can name 3+ plausible features it rules out. If you can't, the pillar is too vague.
- Actionable: Can be used to make decisions ("Does this feature serve this pillar?")
- Memorable: Short enough to recite from memory (2-5 words ideal)
- Unique to your game: Not generic truths ("fun gameplay" is not a pillar)
- In tension with alternatives: Choosing this pillar means NOT choosing its opposite — and you can point to the excluded alternatives
Pillar Formulation Process
Step 1: Identify the Core Fantasy
What emotional experience are you selling? Not mechanics — feelings.
- "The thrill of barely surviving" (not "combat system")
- "Building something beautiful from nothing" (not "crafting mechanics")
Step 2: Define by Exclusion First
For each candidate pillar, write its "What This Rules Out" list BEFORE writing what it approves:
- List 3+ concrete, plausible features or approaches this pillar rejects
- If you can't list 3 things it rejects, the pillar isn't sharp enough yet
- Then list what it approves — but the rejections come first
- Together, the pillars' exclusion lists should describe a game only YOUR game could be
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 · 118 lines · 55 tokens per session scan A 23a828baf6eb
design-pillars is a skill published in the GitHub repository GoogilyBoogily/googilyboogily-claude-power-tools (2 stars, last pushed 4mo ago), licensed MIT. It adds 55 tokens to every session and 1,607 once invoked, about $0.0003 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.