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 technical-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/technical-generate)<a href="https://agentmods.dev/skills/googilyboogily/googilyboogily-claude-power-tools/technical-generate"><img src="https://agentmods.dev/badge/skills/googilyboogily/googilyboogily-claude-power-tools/technical-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/technical-generate"><img src="https://agentmods.dev/badge/skills/googilyboogily/googilyboogily-claude-power-tools/technical-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.00044 | $0.03935 |
| Opus 5 | $0.00022 | $0.01968 |
| Sonnet 5 | $0.00009 | $0.00787 |
| Haiku 4.5 | $0.00004 | $0.00394 |
Grade A, and why
technical-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 — 500 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Technical & Production Generator
Generate the Technical & Production phase (Phase 5) documents 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
Parse Arguments
Extract from $ARGUMENTS:
- Context File: First non-flag argument (e.g.,
docs/game-design-bible/context/technical-context.md) - Output Directory:
--output-dir <path>(default: derived from context file's Bible Directory, i.e.,<bible-dir>/05-technical-production/)
Source Integrity Rules
Every factual claim in these documents must be traceable to the context file.
- Ground every claim. Every design statement must trace back to a specific entry in the context file (user answers, pillar definitions, prior phase content, or web research with URLs).
- Flag ungrounded claims. If you need to state something not in the context file, mark it explicitly as
[ASSUMPTION]in the document. - Never invent details. If the context file doesn't cover something, put it in Open Questions — don't fabricate.
Process
Step 1: Read Context and Pillars
- Read the context file at the path provided in
$ARGUMENTS. - Read
<bible-dir>/DESIGN-PILLARS.md(derive bible-dir from the context file's Bible Directory field). - Extract:
- Engine & tools, team structure, timeline, monetization
- Technical constraints and asset pipeline
- Prior phase summary with file counts and scope assessment
- All design pillars with definitions
- Web research findings
- Open questions
Step 2: Create Output Directory
mkdir -p <output-dir>
Use Glob to verify <output-dir> exists.
Step 3: Generate engine-and-tools.md
Write <output-dir>/engine-and-tools.md following this structure:
# Engine & Tools — [Game Name]
> **Pillar Alignment:** [which design pillars the engine/tools choices serve]
## Overview
[2-3 paragraphs summarizing the engine choice, development stack, and team structure. Explain how these choices align with the game's scope and design pillars.]
## Engine Choice
### [Engine Name]
- **Version:** [version, if specified]
- **Why This Engine:** [Rationale grounded in genre, platform, team experience, and design pillars. Reference web research findings.]
- **Key Strengths for This Project:** [Specific capabilities that serve this game type]
- **Known Limitations:** [Limitations relevant to this project and mitigation strategies]
### Recommended Packages / Plugins
[Based on web research — list relevant extensions, packages, or plugins with brief descriptions]
| Package | Purpose | Source |
|---------|---------|--------|
| [name] | [what it provides] | [URL from research] |
## Development Tools
| Category | Tool | Purpose |
|----------|------|---------|
| IDE | [tool] | [primary development environment] |
| Version Control | [tool] | [source control] |
| Project Management | [tool] | [task tracking, planning] |
| Art Creation | [tool(s)] | [asset creation] |
| Audio | [tool(s)] | [audio creation/middleware] |
| CI/CD | [tool(s)] | [build automation] |
## Team Structure
[Team composition, roles, and responsibilities]
| Role | Count | Responsibilities |
|------|-------|-----------------|
| [role] | [number] | [key responsibilities] |
### Workflow
[How the team collaborates — branching strategy, review process, asset handoff pipeline]
## Technical Constraints
### Platform Requirements
[Platform-specific constraints from the context file — hardware, OS, store requirements]
### Performance Targets
| Metric | Target | Rationale |
|--------|--------|-----------|
| Frame Rate | [target FPS] | [why this target] |
| Load Times | [target] | [why this target] |
| File Size | [budget] | [platform constraint or distribution reason] |
| Memory | [budget] | [minimum spec target] |
### Minimum Spec
[Minimum hardware/software requirements, if defined]
## Design Rationale
[Why this technical stack was chosen over alternatives. Reference web research for engine comparison data. Explain how the stack serves the design pillars.]
## Open Questions
- [Technical unknowns, unresolved decisions, risks]
## Cross-References
- **Design Pillars:** [path to DESIGN-PILLARS.md]
- **Concept:** [paths to 00-concept/ files]
- **Asset Breakdown:** [path to asset-breakdown.md]
- **Timeline:** [path to timeline.md]
- **Context File:** [path to context file]
## Changelog
| Date | Change | Reason |
|------|--------|--------|
| [today] | Initial creation | Phase 5 — Technical & Production |
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 · 500 lines · 44 tokens per session scan A a1c2d23abadc
technical-generate is a skill published in the GitHub repository GoogilyBoogily/googilyboogily-claude-power-tools (2 stars, last pushed 4mo ago), licensed MIT. It adds 44 tokens to every session and 3,935 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.