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 gdd-writergit 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/gdd-writer)<a href="https://agentmods.dev/skills/simone-tarantino/godot-superpowers/gdd-writer"><img src="https://agentmods.dev/badge/skills/simone-tarantino/godot-superpowers/gdd-writer/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/gdd-writer"><img src="https://agentmods.dev/badge/skills/simone-tarantino/godot-superpowers/gdd-writer.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.00056 | $0.01295 |
| Opus 5 | $0.00028 | $0.00647 |
| Sonnet 5 | $0.00011 | $0.00259 |
| Haiku 4.5 | $0.00006 | $0.00129 |
Grade A, and why
gdd-writer 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 12d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GDD Writer
Maintains the Game Design Document at docs/design/<YYYY-MM-DD>-<slug>-gdd.md. Keeps design (what the game is and why) separate from implementation (how the code works).
Core rule: the GDD drives the code. If code diverges from the GDD, document the divergence in PROGRESS.md (or NOTES.md); never silently rewrite the GDD to match code.
File path convention
- Location:
docs/design/ - Filename:
<YYYY-MM-DD>-<slug>-gdd.md(date is the GDD's first-write date; slug is kebab-case of the working title). - One GDD per project. On major scope rewrites, write a NEW dated file rather than editing the old one — keep the trail. The plan file (
docs/plans/<YYYY-MM-DD>-<slug>-plan.md) references the GDD path.
Standard GDD sections
If no GDD exists, create one with these sections. Skip sections that don't apply to the genre.
| Section | Content | Update when |
|---|---|---|
| Concept (one line) | High-level pitch, tagline | Vision changes |
| Pillars | 3–5 design pillars driving every decision | Foundational shift |
| Tone & Identity | Aesthetic, mood, references | Art/audio direction shifts |
| Player Fantasy | What the player is and what they feel | Core fantasy refined |
| Genre & References | Genre tags, comparables ("X meets Y") | Repositioning |
| Core Loop | The 30-second moment-to-moment loop | Loop refined |
| Meta Loop | Run/session structure, progression between sessions | Meta added/changed |
| Mechanics | Each mechanic: rule, input, output | Mechanic added/changed |
| Systems | How mechanics combine (combat, economy, AI) | System designed |
| Controls | Input scheme per device | Mapping changes |
| Content | Levels, characters, items, enemies (lists) | Content added |
| Progression | XP, unlocks, difficulty curve | Progression tuned |
| Economy | Currencies, sources, sinks, faucets | Economy changed |
| Win/Lose Conditions | Per session, per run, per arena | Conditions change |
| Narrative | Story beats, characters, world | Story drafted |
| UI/UX | Diegetic vs non-diegetic, key screens | UI redesigned |
| Art Direction | Palette, style, references | Art bible refined |
| Audio Direction | Music style, SFX philosophy | Audio direction set |
| Scope | What's in V1, what's cut, stretch goals | Scope decisions |
| Open Questions | [HYPOTHESIS] items still being playtested |
Hypothesis confirmed/discarded |
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.
- 12d ago First seen · 113 lines · 56 tokens per session scan A de650f7d5654
gdd-writer is a skill published in the GitHub repository Simone-Tarantino/godot-superpowers (2 stars, last pushed 4mo ago), licensed MIT. It adds 56 tokens to every session and 1,295 once invoked, about $0.0003 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…