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/simone-tarantino/godot-superpowers/codebase-surveynpx skills add Simone-Tarantino/godot-superpowers --skill codebase-surveygit 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/codebase-survey)<a href="https://agentmods.dev/skills/simone-tarantino/godot-superpowers/codebase-survey"><img src="https://agentmods.dev/badge/skills/simone-tarantino/godot-superpowers/codebase-survey.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.00077 | $0.02021 |
| Opus 5 | $0.00039 | $0.01010 |
| Sonnet 5 | $0.00015 | $0.00404 |
| Haiku 4.5 | $0.00008 | $0.00202 |
Grade A, and why
codebase-survey 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.
How it starts
The opening of the file, as written. The whole thing — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codebase Survey
Maps the parts of an existing Godot project that a planned feature will touch. Output anchors the downstream feature-spec and feature-plan to real files, real APIs, and real risks — not to memory or wishful thinking.
Core rule: read-only. This skill never edits .gd, .tscn, .tres, or .gdshader. It writes exactly one file: docs/features/<YYYY-MM-DD>-<slug>-survey.md.
When to invoke
- A user asks to add / change / extend a feature on a project that already has code.
- The change touches 2+ files OR 1+ autoload OR 1+ existing scene.
- Before
feature-spec— survey is the input the spec depends on.
Skip the survey for:
- Trivial features under the shared shortcut: touches one file AND adds no new mechanic AND adds no new public surface (no new signal / exported var / autoload / input action). In that case,
feature-specrecordsSurvey reference: none (trivial shortcut)andfeature-planaccepts the same string. Any of the three conditions failing makes the survey mandatory. - Greenfield projects (no code yet — use
game-brainstorming→gdd-writerinstead). - Read-only investigations (use the
Exploreagent).
File path convention
- Location:
docs/features/ - Filename:
<YYYY-MM-DD>-<slug>-survey.md- Date is the day the survey is written.
- Slug is kebab-case of the feature working title (e.g.
2026-05-12-double-jump-survey.md).
- One survey per feature. When re-surveying after major project changes, write a NEW dated file rather than editing — keep the trail.
- The matching
feature-specandfeature-planreuse the same<YYYY-MM-DD>-<slug>prefix:docs/features/<YYYY-MM-DD>-<slug>-feature.mddocs/plans/<YYYY-MM-DD>-<slug>-feature-plan.md
Inputs
- The user's feature description (one or two sentences is fine — survey expands it).
- The existing project tree (
project.godot,scenes/,scripts/,autoload/,resources/). - The latest GDD (
docs/design/*-gdd.md) if one exists — link it so the spec inherits design pillars.
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 · 158 lines · 77 tokens per session scan A 3df26e801230
codebase-survey is a skill published in the GitHub repository Simone-Tarantino/godot-superpowers (2 stars, last pushed 4mo ago), licensed MIT. It adds 77 tokens to every session and 2,021 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…
yume-asset-designer
Visual + audio + UI-style designer for Yume games. Picks ONE consistent strategy per project (library lookup / AI-gen prompt / code-draw shape) for visuals; writes audio cue mappings and localized strings. Per ADR 0009 — owns audio/cues.json (semantic event → sound name) and ui/strings.json (localizable HUD text), in…
yume-design
Run the Yume text-to-game pipeline. Orchestrates 7 specialist skills (yume-game-designer → game-planner → systems-designer → content-designer → asset-designer → qa-tester, plus tech-director on demand) with optional user-approval gates. Skills load into orchestrator context (no subagent spawn — Tier 2.6 architecture).…
yume-content-designer
Entities + initial state designer for Yume games. Translates GDD + world plan into entity definitions (entities/.json), initial placements (per-level entities.json), and world initial state (world/state.json). Picks tag names, state field names, default values, positions. Per ADR 0009 — narrowed scope: rules are NOT…
yume-game-reviewer
Adversarial reviewer for Yume GDDs. Reads docs/games/ /GDD.md and applies critical-but-fair scrutiny across 15 depth axes (mechanical/strategic/pacing/feedback/aesthetic/scope/adversarial + total content scope, signature moments, theme/identity, replay value, real-UX, spatial-design/level-layout). Outputs review.md…