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 AshExplained/roblox-skills --skill roblox-debugging-bugfixgit clone --depth 1 https://github.com/AshExplained/roblox-skillsWrote 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/ashexplained/roblox-skills/roblox-debugging-bugfix)<a href="https://agentmods.dev/skills/ashexplained/roblox-skills/roblox-debugging-bugfix"><img src="https://agentmods.dev/badge/skills/ashexplained/roblox-skills/roblox-debugging-bugfix/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/ashexplained/roblox-skills/roblox-debugging-bugfix"><img src="https://agentmods.dev/badge/skills/ashexplained/roblox-skills/roblox-debugging-bugfix.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.00058 | $0.01152 |
| Opus 5.5 | $0.00023 | $0.00461 |
| Sonnet 5.5 | $0.00012 | $0.00230 |
| Haiku 4.5 | $0.00006 | $0.00115 |
Grade A, and why
roblox-debugging-bugfix 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 1mo 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Roblox Debugging Bugfix
Goal
Move from symptom to verified fix without guessing. For hard or intermittent bugs, follow the discipline below; skip phases only when you can justify it.
Phase 1 — Build a repro loop first (this is the skill)
Everything else is mechanical once you have a fast, repeatable pass/fail signal for the bug. Spend disproportionate effort here. Be aggressive and creative before you touch a fix.
Ways to construct one, roughly in order:
- Studio playtest repro — the exact steps in Play mode that surface the bug; watch
get_console_output. execute_luauharness — call the suspect server/module function directly with a fixture input and assert the result, instead of clicking through the whole game.- Targeted scenario — spawn the minimal instances/state that trigger the code path (one part, one remote, one player state).
- Replay a captured payload — save the real remote payload / data profile that misbehaves and push it back through the code path in isolation.
Make the loop fast, sharp, and deterministic: narrow to the specific symptom, pin any randomness/timing, and cut unrelated setup. A 2-second deterministic check beats a 30-second flaky one.
Intermittent bugs: the goal is a higher reproduction rate, not a clean one-shot. Loop the trigger many times, add stress, narrow timing windows. A 50%-flake bug is debuggable; keep raising the rate until it is.
If you genuinely cannot build a loop, stop and say so — list what you tried and ask the user for the environment, a captured artifact (log dump, screen recording with timestamps, the offending data), or permission to add temporary instrumentation. Do not hypothesize without a loop.
Phase 2 — Reproduce
Run the loop. Confirm it produces the failure the user described (not a nearby lookalike), that it repeats, and that you've captured the exact symptom for later verification.
Phase 3 — Hypothesize
Generate 3–5 ranked, falsifiable hypotheses before testing any — single-hypothesis debugging anchors on the first guess. Each states a prediction: "If X is the cause, then changing Y makes it disappear." Show the ranked list to the user before probing; they often re-rank instantly ("we just changed #3"). Proceed on your ranking if they're AFK.
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.
- 1mo ago First seen · 91 lines · 58 tokens per session scan A 16a488f98949
roblox-debugging-bugfix is a skill published in the GitHub repository AshExplained/roblox-skills (29 stars, last pushed 3mo ago), licensed MIT. It adds 58 tokens to every session and 1,152 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
tang-rou
Ative TANG-ROU (Soft Mist) quando o usuário nomear TANG-ROU ou pedir desenvolvimento, correção, auditoria, otimização ou planejamento de Foundry VTT e programação aplicada: macros, módulos, sistemas, CSB, Combat Tracker Dock, Midi-QOL, DAE, Sequencer, Warp Gate, Active Effects, hooks, compêndios, fichas homebrew, erro…
consistency-check
Scan GDDs against the entity registry for cross-document conflicts. Grep-first approach targets conflicting sections, different stats.
performance-optimization
Find and fix game performance problems methodically — measure with the engine profiler first, reason about the frame-time budget, locate the CPU-vs-GPU bottleneck, then apply the right fix: object pooling, draw-call batching, fewer allocations/GC spikes, and asset budgets. Engine- neutral method that pairs with each…
godot-debugging
Use when debugging Godot projects — remote debugger, print techniques, signal tracing, common error patterns and fixes.
beehave
Use when using the Beehave addon — pure-GDScript behavior trees with composites, decorators, leaves, a blackboard, and a visual runtime debugger.
ast-grep
Searches and rewrites code by AST shape across 25 languages. Use when the target is a syntax pattern (every call/class/import shaped like X, a codemod, a YAML rule) rather than literal text; for plain strings, comments, or filenames, use rg.