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 Simone-Tarantino/godot-superpowers --skill feature-specgit clone --depth 1 https://github.com/Simone-Tarantino/godot-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/simone-tarantino/godot-superpowers/feature-spec)<a href="https://agentmods.dev/skills/simone-tarantino/godot-superpowers/feature-spec"><img src="https://agentmods.dev/badge/skills/simone-tarantino/godot-superpowers/feature-spec/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/simone-tarantino/godot-superpowers/feature-spec"><img src="https://agentmods.dev/badge/skills/simone-tarantino/godot-superpowers/feature-spec.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.00085 | $0.02224 |
| Opus 5 | $0.00043 | $0.01112 |
| Sonnet 5 | $0.00017 | $0.00445 |
| Haiku 4.5 | $0.00009 | $0.00222 |
Grade A, and why
feature-spec 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 9d 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 — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature Spec
Surgical design document for one bounded feature added to an existing game. Lives between the GDD (whole game) and the plan (technical decomposition).
When to invoke
- After
codebase-surveyfinishes, on a project that already has code. - The change is bounded enough to fit in one document (one mechanic, one system tweak, one UI screen).
- A GDD already exists for the project — the feature inherits its pillars.
Do NOT use this skill for:
- Greenfield projects — use
game-brainstorming→gdd-writer(full GDD). - Cross-cutting refactors touching every system — that's a re-plan; escalate to Trail A: redo
game-brainstorming→gdd-writer→writing-game-planfrom scratch. Do NOT silently mutate a feature spec into a whole-game plan. - Bug fixes with a known repro — direct edit +
code-reviewer.
File path convention
- Location:
docs/features/ - Filename:
<YYYY-MM-DD>-<slug>-feature.md(same<YYYY-MM-DD>-<slug>prefix used by the matching survey). - One spec per feature. Major scope rewrites get a NEW dated file; never edit historical specs.
- The plan file is
docs/plans/<YYYY-MM-DD>-<slug>-feature-plan.mdand references this spec by path.
Inputs
- The survey:
docs/features/<YYYY-MM-DD>-<slug>-survey.md— strongly recommended, optional only under the trivial-feature shortcut below. - The current GDD:
docs/design/*-gdd.md(latest). - The user's feature description (one or two sentences).
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.
- 9d ago First seen · 196 lines · 85 tokens per session scan A 2a1739e14801
feature-spec is a skill published in the GitHub repository Simone-Tarantino/godot-superpowers (2 stars, last pushed 4mo ago), licensed MIT. It adds 85 tokens to every session and 2,224 once invoked, about $0.0004 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
game-build-team
Build a Godot 4 / GDScript game feature with a coordinated agent team — a Manager (you), a Creative Director, a Logic Developer, an Animation Developer, and a Tester — that iteratively and autonomously design, build, juice, and verify the feature against the project's design contract to a strict, un-skippable quality…
avatar-contribution-pr
Turn an avatar GitHub issue (from the in-app avatar-editor easter egg) into a merged sprite — validate the art, then either add a new module or replace an existing one, and open a PR that closes the issue. Handles both "Avatar contribution: " (a brand-new sprite) and "Avatar edit: " (a hand-redraw of an existing…
wavedash
Use when building, integrating, testing, uploading, publishing, or preparing a browser game for Wavedash, including CLI setup, Wavedash SDK features, multiplayer, achievements, leaderboards, cloud saves, player identity, user-generated content, store metadata, monetization, and content guidelines.
godot-engineer
!cat skills/shared/protocols/3d-spatial-foundations.md 2>/dev/null || true !cat skills/shared/game-visual-foundations.md 2>/dev/null || echo "=== Visual Foundations not loaded ===" !cat skills/shared/protocols/ux-protocol.md 2>/dev/null || true !cat skills/shared/protocols/game-test-protocol.md 2>/dev/null || true…
bootstrap-game-qa-system
Use ONCE per browser-game project to set up the game-qa infrastructure. Copies the shipped runner template, the adapter skeleton, and the journey schema; gap-fills the project's existing debug system if one is present. Skip for non-game projects.
requesting-game-qa
Use ONLY for QA on browser-game feature work. Triggers when the engineer signals readiness for QA: "request QA on X", "verify X", "QA this", "ready for QA on X", "this should be ready, can we make sure it works?" Compiles a brief, drives test-plan sign-off, then hands off to game-qa. Skip for tooling, build scripts…