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-orchestratorgit 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-orchestrator)<a href="https://agentmods.dev/skills/mike007jd/game-superpowers/gsp-orchestrator"><img src="https://agentmods.dev/badge/skills/mike007jd/game-superpowers/gsp-orchestrator/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-orchestrator"><img src="https://agentmods.dev/badge/skills/mike007jd/game-superpowers/gsp-orchestrator.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.00029 | $0.01033 |
| Opus 5 | $0.00015 | $0.00517 |
| Sonnet 5 | $0.00006 | $0.00207 |
| Haiku 4.5 | $0.00003 | $0.00103 |
Grade A, and why
gsp-orchestrator 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Using Game Superpowers
Collection entrypoint. Classify the request, then route explicitly.
Classification
- Build — new project, prototype, feature, vertical slice
- Audit — diagnosis, read-only review, risk or UX review
- Repair — targeted fixes after diagnosis
- Polish — working game, better feel / UX / feedback / quality
Project state:
greenfieldprelaunchshippedlive-risky
Output strategy
Choose one before invoking downstream skills:
- inline (default) — keep findings and plans in conversation; do not write
docs/. - minimal — persist only the small set of files needed for cross-session continuity.
- full — write all requested docs artifacts.
Default to inline unless the user explicitly wants docs or the project clearly needs them. This overrides downstream defaults.
Routing
Build
gsp-concept-brainstormwhen fantasy or goals are unclear, and by default for one-prompt generation, showcase builds, benchmark runs, or archetype-led requests such asrunner,platformer,survivor,shooter,breakout,fps,dungeon crawler, orarenagsp-scope-profilegsp-build-strategygsp-super-build
Add as needed:
gsp-douyin-h5for explicit Douyin-style portrait H5 deliverygsp-ux-flow-designer,gsp-feedback-designgsp-loop-bootstrap,gsp-mechanics-systems-designgsp-build-review,gsp-subagent-build-loopgsp-web-2d-specialist,gsp-web-3d-specialistgsp-polished-prototype,gsp-production-feature
Audit
gsp-project-state-assessmentgsp-project-auditgsp-audit-scorecardgsp-repair-roadmap
Add the matching audit skills:
gsp-ux-flow-audit,gsp-hud-readability-auditgsp-feedback-audit,gsp-audio-feedback-audit,gsp-feel-auditgsp-mechanics-systems-audit,gsp-scope-completeness-auditgsp-production-readiness-audit,gsp-architecture-maintainability-auditgsp-live-risk-auditwhenproject-state == shippedorproject-state == live-risky
What ships with it
5 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.
- 10d ago First seen · 92 lines · 29 tokens per session scan A 05cc22fb3094
gsp-orchestrator is a skill published in the GitHub repository mike007jd/game-superpowers (12 stars, last pushed 4mo ago), licensed MIT. It adds 29 tokens to every session and 1,033 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
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.