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-super-buildgit 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-super-build)<a href="https://agentmods.dev/skills/mike007jd/game-superpowers/gsp-super-build"><img src="https://agentmods.dev/badge/skills/mike007jd/game-superpowers/gsp-super-build/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-super-build"><img src="https://agentmods.dev/badge/skills/mike007jd/game-superpowers/gsp-super-build.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.00027 | $0.00553 |
| Opus 5 | $0.00014 | $0.00277 |
| Sonnet 5 | $0.00005 | $0.00111 |
| Haiku 4.5 | $0.00003 | $0.00055 |
Grade A, and why
gsp-super-build 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 11d 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 — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Game Super Build
Lead game-production workflow. Choose the right strategy for project state and quality target instead of just producing the smallest thing that runs.
Outputs
Follow the gsp-orchestrator output strategy:
- inline (default): keep all findings, plans, and decisions in conversation. Do not create
docs/files. - minimal: write only
docs/game-studio/plan.mdanddocs/game-studio/quality-target.mdfor cross-session continuity. - full: create or update the relevant
docs/game-studio/records for project state, concept, requirements, scope, build strategy, backend, UX, feedback, architecture, plan, quality, and release safety.
Phase map
- Classify
- Detect build, audit, or both.
- Existing repo inspection routes to
gsp-project-auditfirst. - Assess project state with
gsp-project-state-assessment.
- Lock the brief
- Use
gsp-concept-brainstormwhen the request is vague, weakly differentiated, archetype-ambiguous, or a one-prompt showcase build. - Use
gsp-requirements-brainstorm. - Use
gsp-scope-profile. - Use
gsp-build-strategy.
- Use
- Choose implementation route
- Use
gsp-backend-selector. - Route explicit Douyin H5 delivery through
gsp-douyin-h5before deeper browser specialization. - Route chosen web 2D or browser 3D profiles to the matching specialist skill.
- Use
- Design the product
- Use
gsp-ux-flow-designer,gsp-feedback-design, andgsp-mechanics-systems-design. - Use
gsp-production-codewhen the quality target needs product-grade implementation standards.
- Use
- Execute and verify
- Use
gsp-implementation-plan. - If subagents are available and the target is above throwaway-spike quality, prefer
gsp-subagent-build-loop. - Review and verify with
gsp-build-review,gsp-playability-verifier, andgsp-screenshot-critic.
- Use
- Escalate only when justified
- Use compare or rolling-supervisor modes only when the task size or uncertainty warrants them.
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.
- 11d ago First seen · 44 lines · 27 tokens per session scan A d7169b4100ac
gsp-super-build is a skill published in the GitHub repository mike007jd/game-superpowers (12 stars, last pushed 4mo ago), licensed MIT. It adds 27 tokens to every session and 553 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.