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 agentmods add skills/mike007jd/game-superpowers/gsp-loop-bootstrapnpx skills add mike007jd/game-superpowers --skill gsp-loop-bootstrapgit 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-loop-bootstrap)<a href="https://agentmods.dev/skills/mike007jd/game-superpowers/gsp-loop-bootstrap"><img src="https://agentmods.dev/badge/skills/mike007jd/game-superpowers/gsp-loop-bootstrap.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.00222 |
| Opus 5 | $0.00013 | $0.00111 |
| Sonnet 5 | $0.00005 | $0.00044 |
| Haiku 4.5 | $0.00003 | $0.00022 |
Grade A, and why
gsp-loop-bootstrap 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 5d 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 Loop Bootstrap
Goal
Create a maintainable gameplay architecture that matches the chosen target quality.
Outputs
Follow the gsp-orchestrator output strategy:
- inline (default): present architecture decisions in conversation.
- minimal or full: write or update
docs/game-studio/architecture.md.
Prefer abstractions like
GameManagerInputProfileStateMachinePlayerControllerCameraRigHUDFlowSoundLayerEncounterDirector
Rules
- Separate simulation state and UI state clearly enough to reason about them.
- Avoid hiding critical gameplay state inside presentation objects.
- Choose the simplest architecture that still supports the requested result.
- In aggressive greenfield modes, do not fear building a complete coherent shell if it prevents later churn.
- In live modes, preserve compatibility unless a deliberate migration plan exists.
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.
- 5d ago First seen · 33 lines · 25 tokens per session scan A bcfb54cb4668
gsp-loop-bootstrap 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 222 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
design-system
Guided, section-by-section GDD authoring for a single game system. Gathers context from existing docs, walks through each required section collaboratively, cross-references dependencies, and writes incrementally to file.
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.
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…
gate-check
Validate readiness to advance between development phases. Produces a PASS/CONCERNS/FAIL verdict with specific blockers and required artifacts. Use when user says 'are we ready to move to X', 'can we advance to production', 'check if we can start the next phase', 'pass the gate'.
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…