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 mike007jd/game-superpowers --skill gsp-implementation-plangit clone --depth 1 https://github.com/mike007jd/game-superpowersWrote 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/mike007jd/game-superpowers/gsp-implementation-plan)<a href="https://agentmods.dev/skills/mike007jd/game-superpowers/gsp-implementation-plan"><img src="https://agentmods.dev/badge/skills/mike007jd/game-superpowers/gsp-implementation-plan.svg" alt="Measured on agentmods" 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.00025 | $0.00293 |
| Opus 5 | $0.00013 | $0.00147 |
| Sonnet 5 | $0.00005 | $0.00059 |
| Haiku 4.5 | $0.00003 | $0.00029 |
Grade A, and why
gsp-implementation-plan 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 7d 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.
What it actually says
Game Implementation Plan
Turn the approved build brief into an execution plan.
Use ./shared/templates/task-plan.md.
Outputs
Follow the gsp-orchestrator output strategy:
- inline (default): present implementation plan in conversation.
- minimal or full: write
docs/game-studio/plan.md.
Key rule
Do not use one default task size for all situations. Use the chosen development mode.
Planning bias
- In yolo-super, larger end-to-end tasks are allowed and often preferred.
- In guided-build, keep the plan comprehensible but still fast.
- In refactor-open, plan migrations and replacements explicitly.
- In surgical-live, keep tasks tight and rollbackable.
Execution bias
Unless the user explicitly wants a cheap or minimal pass, assume the plan should support:
- a builder stage
- a reviewer stage
- a verifier stage
For benchmark, showcase, or polished-prototype work, plan with this loop in mind instead of assuming one pass from build to done.
Important
Do not produce fake progress tasks like “set up scaffolding” unless that scaffold immediately enables real implementation. Prefer tasks that end in a stronger running build.
What ships with it
6 files 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.
- 7d ago First seen · 38 lines · 25 tokens per session scan A 5455a7ab30be
gsp-implementation-plan is a skill published in the GitHub repository mike007jd/game-superpowers (6 stars, last pushed 4mo ago), licensed MIT. It adds 25 tokens to every session and 293 once invoked, about $0.0001 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-08-31.
Other skills, from other repositories
setup-engine
Configure the project's game engine and version. Pins the engine in CLAUDE.md, detects knowledge gaps, and populates engine reference docs via WebSearch when the version is beyond the LLM's training data.
ux-design
Guided, section-by-section UX spec authoring for a screen, flow, or HUD. Reads game concept, player journey, and relevant GDDs to provide context-aware design guidance. Produces ux-spec.md (per screen/flow) or hud-design.md using the studio templates.
architecture-review
Validates completeness and consistency of the project architecture against all GDDs. Builds a traceability matrix mapping every GDD technical requirement to ADRs, identifies coverage gaps, detects cross-ADR conflicts, verifies engine compatibility consistency across all decisions, and produces a PASS/CONCERNS/FAIL…
prototype
Concept prototype — validate the core idea is worth designing before writing GDDs. Run right after /brainstorm and /setup-engine. Routes to HTML, Engine, or Paper path based on game type. Produces a throwaway build and a PROCEED/PIVOT/KILL verdict.
review-all-gdds
Holistic cross-GDD consistency and game design review. Reads all system GDDs simultaneously and checks for contradictions between them, stale references, ownership conflicts, formula incompatibilities, and game design theory violations (dominant strategies, economic imbalance, cognitive overload, pillar drift). Run…
localize
Full localization pipeline: scan for hardcoded strings, extract and manage string tables, validate translations, generate translator briefings, run cultural/sensitivity review, manage VO localization, test RTL/platform requirements, enforce string freeze, and report coverage.