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 update-docsgit 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/update-docs)<a href="https://agentmods.dev/skills/simone-tarantino/godot-superpowers/update-docs"><img src="https://agentmods.dev/badge/skills/simone-tarantino/godot-superpowers/update-docs.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.00080 | $0.02147 |
| Opus 5 | $0.00040 | $0.01073 |
| Sonnet 5 | $0.00016 | $0.00429 |
| Haiku 4.5 | $0.00008 | $0.00215 |
Grade A, and why
update-docs 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 6d 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 — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update Project Docs
Keeps every project doc in sync — both the core docs (README, GDD, whole-game plan, PROGRESS, CLAUDE) and any feature artifacts (surveys, specs, feature plans) that exist. Only touches the ones that are present; does not force a project to adopt every doc type.
Doc set (core + feature artifacts)
| Doc | Purpose | Update when |
|---|---|---|
README.md |
What the project is, how to run it, top-level overview | Tech stack changes, install steps change |
docs/design/<YYYY-MM-DD>-<slug>-gdd.md |
Game Design Document — design intent | Design decisions made (use gdd-writer) |
docs/plans/<YYYY-MM-DD>-<slug>-plan.md |
Whole-game implementation plan — milestones, skills, deliverables | Plan revised (use writing-game-plan) |
docs/features/<YYYY-MM-DD>-<slug>-survey.md |
Feature codebase survey — files / APIs / hotspots | Whenever a new feature lands on existing code (use codebase-survey) |
docs/features/<YYYY-MM-DD>-<slug>-feature.md |
Feature spec — design delta on top of GDD | New feature designed (use feature-spec) |
docs/plans/<YYYY-MM-DD>-<slug>-feature-plan.md |
Feature implementation plan | Feature plan revised (use feature-plan) |
PROGRESS.md |
Status: GDD/spec → code mapping, divergences | After every implementation |
CLAUDE.md |
Architecture and conventions for Claude Code | New subsystem, new convention, new module |
PROGRESS.md and CLAUDE.md are optional but recommended on any project larger than ~10 scenes. The docs/features/* trio only exists on projects that adopt feature-mode (trail B).
Decision flow
digraph update_flow {
rankdir=TB;
node [shape=diamond];
start [label="What changed?" shape=doublecircle];
impl [label="Code\nimplemented?"];
design [label="Design\nchanged?"];
arch [label="Architecture\nchanged?"];
setup [label="Setup/install\nchanged?"];
check [label="Cross-check"];
node [shape=box];
progress [label="Update PROGRESS.md\n(checkbox feature)"];
gdd [label="Update GDD\n(docs/design/...-gdd.md)"];
claudemd [label="Update CLAUDE.md\n(arch / convention)"];
readme [label="Update README.md\n(install / overview)"];
cross [label="Verify docs agree"];
start -> impl;
impl -> progress [label="yes"];
impl -> design [label="no"];
design -> gdd [label="yes"];
progress -> design;
gdd -> arch;
design -> arch [label="no"];
arch -> claudemd [label="yes"];
arch -> setup [label="no"];
claudemd -> setup;
setup -> readme [label="yes"];
setup -> check [label="no"];
readme -> check;
check -> cross;
}
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.
- 6d ago First seen · 184 lines · 80 tokens per session scan A 0f7f66032b34
update-docs is a skill published in the GitHub repository Simone-Tarantino/godot-superpowers (2 stars, last pushed 4mo ago), licensed MIT. It adds 80 tokens to every session and 2,147 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…