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 concept-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/concept-generate)<a href="https://agentmods.dev/skills/googilyboogily/googilyboogily-claude-power-tools/concept-generate"><img src="https://agentmods.dev/badge/skills/googilyboogily/googilyboogily-claude-power-tools/concept-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/concept-generate"><img src="https://agentmods.dev/badge/skills/googilyboogily/googilyboogily-claude-power-tools/concept-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.00047 | $0.02440 |
| Opus 5 | $0.00023 | $0.01220 |
| Sonnet 5 | $0.00009 | $0.00488 |
| Haiku 4.5 | $0.00005 | $0.00244 |
Grade A, and why
concept-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 — 298 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Concept Phase — Document Generator
Generate the complete Concept phase (Phase 0) of a Game Design Bible from a previously gathered context file. This skill runs with clean context and is non-interactive — all questions were answered during the gather phase.
Input
$ARGUMENTS — path to the context file (e.g., docs/game-design-bible/context/concept-context.md), and optionally:
--output-dir <path>— override the output directory from the context file
Parse Arguments
Extract from $ARGUMENTS:
- Context File: First non-flag argument
- Output Dir:
--output-dir <path>, or extracted from the context file'sOutput Dirfield
Source Integrity Rules
Every factual claim in these documents must be traceable to the context file.
- Ground every claim. Every statement must trace back to the context file — user answers, MDA analysis, web research with URLs, or design pillar deliberations.
- Flag ungrounded claims. If you need to state something not in the context file, mark it explicitly as
[ASSUMPTION]. - Never invent details. If the context file doesn't cover something, put it in Open Questions — don't fabricate.
Process
Step 1: Read Inputs
- Read the context file from
$ARGUMENTS. - Extract all gathered information:
- Game concept, scope, core fantasy
- Genre & platform details
- Design pillars with "What This Rules Out" lists
- Non-goals
- MDA analysis (aesthetics, dynamics, mechanics)
- Web research findings
- Open questions
- Output directory
Step 2: Create Directory Structure
mkdir -p <output-dir>/00-concept
mkdir -p <output-dir>/01-core-loop
mkdir -p <output-dir>/02-systems
mkdir -p <output-dir>/03-narrative
mkdir -p <output-dir>/04-art-audio
mkdir -p <output-dir>/05-technical-production
mkdir -p <output-dir>/context
mkdir -p <output-dir>/reviews
Step 3: Generate Documents
Generate these files in order. Every section file follows this template structure:
# [Title]
> **Pillar Alignment:** [Which design pillars this section serves]
## Overview
[2-3 paragraph summary]
## Detailed Design
[Section-specific content]
## Design Rationale
[Why these choices were made, grounded in context file]
## Open Questions
- [Unresolved items relevant to this section]
## Cross-References
- [Links to related sections within the bible]
## Changelog
| Date | Change | Reason |
|------|--------|--------|
| [today] | Initial creation | Phase 0 — Concept |
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 · 298 lines · 47 tokens per session scan A b2b1ac616e61
concept-generate 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 2,440 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.