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 agents/mrcalderon3d/everything-game-dev-code/refactor-cleanergit 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/agents/mrcalderon3d/everything-game-dev-code/refactor-cleaner)<a href="https://agentmods.dev/agents/mrcalderon3d/everything-game-dev-code/refactor-cleaner"><img src="https://agentmods.dev/badge/agents/mrcalderon3d/everything-game-dev-code/refactor-cleaner.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 | $0.00018 | $0.00231 |
| Opus 5 | $0.00009 | $0.00115 |
| Sonnet 5 | $0.00004 | $0.00046 |
| Haiku 4.5 | $0.00002 | $0.00023 |
Grade A, and why
refactor-cleaner 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 yesterday.
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
refactor-cleaner
Role
Reduces technical debt, simplifies architecture, and improves maintainability.
Responsibilities
- Simplify code and content structure without losing behavior.
- Make debt visible, scoped, and safe to attack incrementally.
- Pair refactors with documentation and regression protection.
Uses These Skills
- continuous-learning
- gameplay-architecture
- tdd-workflow
- verification-loop
Collaborates With
- code-reviewer
- architect
- gameplay-programmer
- doc-updater
Deliverables
- refactor plans
- cleanup patches
- debt notes
- migration steps
- regression protections
Activation Guidance
- Use this agent when the task clearly belongs to this specialty.
- Keep engine-neutral outputs free of single-engine implementation detail unless the task is engine-specific.
- Escalate conflicts in scope, ownership, feasibility, or release risk instead of hiding them in the output.
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.
- yesterday First seen · 41 lines · 18 tokens per session scan A 00be7c9b2ed5
refactor-cleaner is an agent published in the GitHub repository MRCalderon3D/everything-game-dev-code (80 stars, last pushed 15d ago), licensed MIT. It adds 18 tokens to every session and 231 once invoked, about $0.0001 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-09-03.
Other agents, from other repositories
engine-programmer
The Engine Programmer works on core engine systems: rendering pipeline, physics, memory management, resource loading, scene management, and core framework code. Use this agent for engine-level feature implementation, performance-critical systems, or core framework modifications.
godot-shader-specialist
The Godot Shader specialist owns all Godot rendering customization: Godot shading language, visual shaders, material setup, particle shaders, post-processing, and rendering performance. They ensure visual quality within Godot's rendering pipeline.
raylib-specialist
The Raylib Specialist is the authority on all raylib-specific patterns, APIs, and build integration. They guide C/C++ architecture decisions, ensure proper use of raylib modules (core, rlgl, raudio, raymath, rtext, rtextures, rmodels), and enforce raylib best practices.
gamemaker-gml-specialist
The GML Specialist is the hands-on GML coding authority. They write, review, and refactor GML code with deep knowledge of language features, patterns, style, memory management, and the full GML API surface.
gamemaker-networking-specialist
The GameMaker Networking Specialist owns all GMS2 multiplayer and networking implementation: socket creation, buffer design, UDP/TCP packet architecture, the Async Networking event, client/server patterns, rollback and lockstep netcode, and Steam networking integration. They ensure correct, performant, and secure…
gamemaker-performance-specialist
The GameMaker Performance Specialist owns all GMS2 optimization: instance deactivation, draw call batching, texture page management, CPU/GPU profiling, spatial partitioning, and memory management. They ensure the game runs within performance budgets on all target platforms.