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 MRCalderon3D/everything-game-dev-code --skill godot-signals-patternsgit clone --depth 1 https://github.com/MRCalderon3D/everything-game-dev-codeWrote 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/mrcalderon3d/everything-game-dev-code/godot-signals-patterns)<a href="https://agentmods.dev/skills/mrcalderon3d/everything-game-dev-code/godot-signals-patterns"><img src="https://agentmods.dev/badge/skills/mrcalderon3d/everything-game-dev-code/godot-signals-patterns/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/mrcalderon3d/everything-game-dev-code/godot-signals-patterns"><img src="https://agentmods.dev/badge/skills/mrcalderon3d/everything-game-dev-code/godot-signals-patterns.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.00026 | $0.00351 |
| Opus 5.5 | $0.00010 | $0.00140 |
| Sonnet 5.5 | $0.00005 | $0.00070 |
| Haiku 4.5 | $0.00003 | $0.00035 |
Grade A, and why
godot-signals-patterns 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 10d 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.
What it actually says
Godot Signals Patterns
Purpose
Use signals for decoupling without creating hidden event webs, ownership confusion, or lifecycle bugs.
Use When
- signal usage is growing
- scene communication is brittle
- callbacks and node dependencies are hard to debug
Inputs
- scene architecture
- system boundaries
- signal producers and consumers
- lifecycle notes
Process
- define which signals are stable contracts
- document who connects, disconnects, and owns signal lifetime
- avoid using signals when direct ownership is clearer
- prevent scene-tree timing assumptions from becoming hidden requirements
- add debug support for signal-heavy flows
Outputs
- signal contract list
- ownership notes
- debugging guidance
- anti-pattern warnings
Quality Bar
- respects scene-tree ownership, autoload boundaries, and resource behavior
- keeps scripts, signals, and resources understandable at scale
- supports export reliability and content iteration without hidden coupling
Common Failure Modes
- autoloads becoming global dumping grounds
- signal webs with no ownership
- shared resources causing accidental state leakage
Related Agents
- godot-reviewer
- tools-programmer
- gameplay-programmer
Related Commands
- godot-review
- godot-scene-audit
- refactor-clean
Notes
- Keep this skill aligned with the relevant rules layer and current project documentation.
- If engine-specific constraints materially change the workflow, hand off to the matching engine skill or engine-specific reviewer.
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.
- 10d ago First seen · 60 lines · 26 tokens per session scan A 0aae0dd6bd9b
godot-signals-patterns is a skill published in the GitHub repository MRCalderon3D/everything-game-dev-code (96 stars, last pushed 11d ago), licensed MIT. It adds 26 tokens to every session and 351 once invoked, about $0.0001 per session on Opus 5.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-10-10.
Other skills, from other repositories
asset-audit
Audits game assets for compliance with naming conventions, file size budgets, format standards, and pipeline requirements. Identifies orphaned assets, missing references, and standard violations.
hotfix
Emergency fix workflow that bypasses normal sprint processes with a full audit trail. Creates hotfix branch, tracks approvals, and ensures the fix is backported correctly.
cgs-bug-report
Use for bug report tasks that capture a reproducible bug with environment, steps, expected/actual behavior, severity, evidence, and owner; produce verification evidence, changed or proposed files, and handoff boundaries.
cgs-bug-triage
Use for bug triage tasks that classify bugs by severity, priority, reproduction confidence, owner role, risk, and release impact; produce verification evidence, changed or proposed files, and handoff boundaries.
cgs-bugfix
Use for bugfix tasks that fix a bounded bug with reproduction evidence, minimal change, regression coverage, and handoff notes; produce verification evidence, changed or proposed files, and handoff boundaries.
cgs-dev-story
Use for dev story tasks that turn a design or bug into an implementation-ready story with owner, files, acceptance tests, and dependencies; produce verification evidence, changed or proposed files, and handoff boundaries.