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-spec-driven-planninggit 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-spec-driven-planning)<a href="https://agentmods.dev/skills/mike007jd/game-superpowers/gsp-spec-driven-planning"><img src="https://agentmods.dev/badge/skills/mike007jd/game-superpowers/gsp-spec-driven-planning/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/mike007jd/game-superpowers/gsp-spec-driven-planning"><img src="https://agentmods.dev/badge/skills/mike007jd/game-superpowers/gsp-spec-driven-planning.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.00037 | $0.00631 |
| Opus 5 | $0.00018 | $0.00316 |
| Sonnet 5 | $0.00007 | $0.00126 |
| Haiku 4.5 | $0.00004 | $0.00063 |
Grade A, and why
gsp-spec-driven-planning 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 10d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Game Spec-Driven Planning
Goal
Add a lightweight spec-driven planning layer to a game project without replacing the normal Game Superpowers tracks.
Artifact model
Keep stable capability specs separate from one change's working set.
- Living specs:
specs/<capability>/spec.md
- Change package:
changes/<change-id>/proposal.mdchanges/<change-id>/design.mdchanges/<change-id>/tasks.mdchanges/<change-id>/specs/<capability>/spec.md
Outputs
Follow the gsp-orchestrator output strategy:
- inline (default): keep the proposal, design, and task structure in conversation only.
- minimal: write the change package under
changes/<change-id>/. - full: write the change package and create or update the matching living specs under
specs/<capability>/.
Use:
./shared/reference/spec-driven-workflow.md./shared/templates/change-proposal.md./shared/templates/capability-spec.md./shared/templates/change-design.md./shared/templates/change-tasks.md
Workflow
- Decide whether the request should stay inline or become durable repo artifacts.
- Derive a stable
change-idand 1-3 capability names. - Use
gsp-requirements-brainstormto lock the requirement set when intent is still fuzzy. - Write
proposal.mdfor the user-facing goal, scope, affected capabilities, and acceptance signals. - Write or update the capability delta under
changes/<change-id>/specs/<capability>/spec.md. - Use the design skills needed for the change, then consolidate the result into
design.md. - Use
gsp-implementation-planto producetasks.md.
Routing
Typical downstream skills:
gsp-requirements-brainstormgsp-mechanics-systems-designgsp-ux-flow-designergsp-feedback-designgsp-implementation-plan
Add gsp-scope-profile, gsp-build-strategy, or gsp-production-code when the change needs stronger scope or quality controls.
Important rules
- Keep
specs/durable and capability-oriented. Do not dump one-off implementation notes into them. - Keep one
changes/<change-id>/folder per meaningful user-facing change. - Put design decisions in
design.md, not intasks.md. - Keep traceability explicit. A proposal should name the capabilities it changes, the design should name the requirements it covers, and tasks should point back to the requirement or design area they implement.
- If the user did not ask for persistent artifacts, do not force file creation.
What ships with it
10 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.
- CHANGELOG.md 170 B
- examples/usage.md 741 B
- MANIFEST.yaml 3.0 KB
- README.md 1.1 KB
- shared/reference/spec-driven-workflow.md 2.7 KB
- shared/templates/capability-spec.md 456 B
- shared/templates/change-design.md 651 B
- shared/templates/change-proposal.md 392 B
- shared/templates/change-tasks.md 386 B
- tests/smoke.md 532 B
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.
- 10d ago First seen · 63 lines · 37 tokens per session scan A f9334c754fb3
gsp-spec-driven-planning is a skill published in the GitHub repository mike007jd/game-superpowers (12 stars, last pushed 4mo ago), licensed MIT. It adds 37 tokens to every session and 631 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-08-31.
Other skills, from other repositories
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…
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…
asset-spec
Generate per-asset visual specifications and AI generation prompts from GDDs, level docs, or character profiles. Produces structured spec files and updates the master asset manifest. Run after art bible and GDD/level design are approved, before production begins.