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-project-auditgit 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-project-audit)<a href="https://agentmods.dev/skills/mike007jd/game-superpowers/gsp-project-audit"><img src="https://agentmods.dev/badge/skills/mike007jd/game-superpowers/gsp-project-audit/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-project-audit"><img src="https://agentmods.dev/badge/skills/mike007jd/game-superpowers/gsp-project-audit.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.00024 | $0.00707 |
| Opus 5 | $0.00012 | $0.00353 |
| Sonnet 5 | $0.00005 | $0.00141 |
| Haiku 4.5 | $0.00002 | $0.00071 |
Grade A, and why
gsp-project-audit 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Game Project Audit
Goal
Audit an existing game project from multiple dimensions before making implementation changes. Default to read-only first.
Default modes
audit-only— produce findings onlyaudit-and-plan— produce findings and a repair roadmapaudit-and-patch— audit first, then patch only approved high-value issues
Outputs
Follow the gsp-orchestrator output strategy:
- inline (default): present all findings, scorecard, and repair directions in conversation. Do not create
docs/files. - minimal: write only
docs/game-studio/audit/audit-summary.mdfor cross-session reference. - full: create and maintain the audit summary, scorecard, UX findings, repair roadmap, and risk register files listed below.
Full output files (when strategy = full):
docs/game-studio/audit/audit-summary.mddocs/game-studio/audit/scorecard.jsondocs/game-studio/audit/ux-findings.mddocs/game-studio/audit/repair-roadmap.mddocs/game-studio/audit/risk-register.md
Use:
./shared/templates/audit-summary.md./shared/templates/audit-scorecard.md./shared/templates/ux-findings.md./shared/templates/repair-roadmap.md./shared/templates/risk-register.md./shared/checklists/project-audit-master-checklist.md./shared/checklists/ui-ux-hard-rules.md./shared/reference/audit-modes.md./shared/reference/audit-confidence-and-evidence.md
Audit workflow
- Assess project state and release risk with
gsp-project-state-assessment. - Determine audit mode and focus dimensions.
- Run the relevant sub-audits:
gsp-ux-flow-auditgsp-hud-readability-auditgsp-feedback-auditgsp-audio-feedback-auditgsp-feel-auditgsp-mechanics-systems-auditgsp-scope-completeness-auditgsp-production-readiness-auditgsp-architecture-maintainability-auditgsp-live-risk-auditwhen the repo is shipped or high-risk
- Consolidate findings with
gsp-audit-scorecard. - If requested, create a prioritized fix plan with
gsp-repair-roadmap. - Patch only after the audit report exists and the requested mode allows edits.
What ships with it
14 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 206 B
- examples/usage.md 605 B
- MANIFEST.yaml 4.1 KB
- README.md 1.3 KB
- shared/checklists/project-audit-master-checklist.md 252 B
- shared/checklists/ui-ux-hard-rules.md 2.2 KB
- shared/reference/audit-confidence-and-evidence.md 477 B
- shared/reference/audit-modes.md 231 B
- shared/templates/audit-scorecard.md 238 B
- shared/templates/audit-summary.md 656 B
- shared/templates/repair-roadmap.md 185 B
- shared/templates/risk-register.md 118 B
- shared/templates/ux-findings.md 635 B
- tests/smoke.md 627 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 · 69 lines · 24 tokens per session scan A e201192686b3
gsp-project-audit is a skill published in the GitHub repository mike007jd/game-superpowers (12 stars, last pushed 4mo ago), licensed MIT. It adds 24 tokens to every session and 707 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.