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 create-resourcegit 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/create-resource)<a href="https://agentmods.dev/skills/simone-tarantino/godot-superpowers/create-resource"><img src="https://agentmods.dev/badge/skills/simone-tarantino/godot-superpowers/create-resource.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.00047 | $0.02089 |
| Opus 5 | $0.00023 | $0.01045 |
| Sonnet 5 | $0.00009 | $0.00418 |
| Haiku 4.5 | $0.00005 | $0.00209 |
Grade A, and why
create-resource 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 8d 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 — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Resource
Generate a custom Resource class so designers (or a future you) can author data as .tres files in the editor instead of hardcoded Dictionary literals.
Why Resources over Dictionaries
| Concern | Dictionary |
Custom Resource |
|---|---|---|
| Type safety | none (Variant) | typed @export fields |
| Editor authoring | code only | Inspector with field hints |
| Validation | runtime checks | @export_range, @export_enum, etc. |
| Refactor rename | grep | rename in script, all .tres re-resolve |
| Save/load | fragile | first-class, ResourceSaver.save |
| Diff in git | unstructured | clean key=value text |
Use Dictionary only for transient runtime payloads (state machine state, signal arguments, network packets).
Template — basic Resource
class_name {Name}
extends Resource
@export var id: StringName
@export var display_name: String
# add fields here
Save to scripts/resources/{snake_case}.gd. Then in the FileSystem dock right-click → New Resource → {Name} to author .tres instances under resources/{plural}/.
Common templates
Item
class_name Item
extends Resource
@export var id: StringName
@export var display_name: String
@export_multiline var description: String
@export var icon: Texture2D
@export var max_stack: int = 1
@export var value: int = 0
@export_enum("Common", "Uncommon", "Rare", "Epic", "Legendary") var rarity: int = 0
@export var tags: Array[StringName] = []
@export var on_use: Script ## script that defines a static use(actor: Node) -> void
Ability / Spell
class_name Ability
extends Resource
@export var id: StringName
@export var display_name: String
@export_multiline var description: String
@export var icon: Texture2D
@export var cooldown: float = 1.0
@export var resource_cost: int = 0 ## mana / energy / stamina
@export_range(0.0, 50.0, 0.5) var range: float = 5.0
@export var damage: int = 0
@export var effect_scene: PackedScene
@export var sound: AudioStream
@export var animation_name: StringName = &""
@export var tags: Array[StringName] = [] ## "fire", "ranged", "channeled"
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.
- 8d ago First seen · 233 lines · 47 tokens per session scan A 44f1615e427a
create-resource is a skill published in the GitHub repository Simone-Tarantino/godot-superpowers (2 stars, last pushed 4mo ago), licensed MIT. It adds 47 tokens to every session and 2,089 once invoked, about $0.0002 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…