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-plangit 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-plan)<a href="https://agentmods.dev/skills/simone-tarantino/godot-superpowers/feature-plan"><img src="https://agentmods.dev/badge/skills/simone-tarantino/godot-superpowers/feature-plan/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-plan"><img src="https://agentmods.dev/badge/skills/simone-tarantino/godot-superpowers/feature-plan.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.00082 | $0.02728 |
| Opus 5 | $0.00041 | $0.01364 |
| Sonnet 5 | $0.00016 | $0.00546 |
| Haiku 4.5 | $0.00008 | $0.00273 |
Grade A, and why
feature-plan 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 — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature Plan
Converts an approved feature spec into an actionable, milestone-based implementation plan that uses the godot-superpowers skill catalog as building blocks. Counterpart of writing-game-plan for changes on top of existing code.
When to invoke
- Immediately after
feature-spechas been approved by the user (the standard handoff). - When picking up a feature that already has a spec but no plan.
- When re-planning after a major scope change to the spec — write a NEW plan file; do not edit the old one.
Inputs
- The feature spec (passed as argument, or located via
docs/features/*-feature.mdof the same slug). Read it fully. The spec's headerSurvey reference:field is canonical:- If it points to a survey file path, that survey is mandatory input — read it fully; it dictates which existing files the plan touches.
- If it is exactly
none (trivial shortcut), the trivial-feature shortcut is in effect (see below). No survey input is required. - Any other value is a drift error — stop and route the user back to
feature-specto repair the header before planning.
- Current project state —
git status,ls, autoloads registered, addons installed.
Trivial-feature shortcut (mirrored from feature-spec)
A feature is trivial iff ALL of: touches one file, adds no new mechanic, adds no new public surface (no new signal / exported var / autoload / input action). The feature-spec declares this by writing Survey reference: none (trivial shortcut) in the spec header.
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 · 215 lines · 82 tokens per session scan A 1a1b986dec9c
feature-plan is a skill published in the GitHub repository Simone-Tarantino/godot-superpowers (2 stars, last pushed 4mo ago), licensed MIT. It adds 82 tokens to every session and 2,728 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…