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 CodePhobiia/claude-roblox-game-studio --skill hotfixgit clone --depth 1 https://github.com/CodePhobiia/claude-roblox-game-studioWrote 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/codephobiia/claude-roblox-game-studio/hotfix)<a href="https://agentmods.dev/skills/codephobiia/claude-roblox-game-studio/hotfix"><img src="https://agentmods.dev/badge/skills/codephobiia/claude-roblox-game-studio/hotfix/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/codephobiia/claude-roblox-game-studio/hotfix"><img src="https://agentmods.dev/badge/skills/codephobiia/claude-roblox-game-studio/hotfix.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.00032 | $0.00897 |
| Opus 5.5 | $0.00013 | $0.00359 |
| Sonnet 5.5 | $0.00006 | $0.00179 |
| Haiku 4.5 | $0.00003 | $0.00090 |
Grade A, and why
hotfix 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/hotfix — Emergency Fix Workflow
Delegate to: release-manager (with technical-director, relevant specialist for actual fix)
When to Use
- Live game broken for many users
- Critical security exploit discovered
- Data loss occurring
- Monetization broken
- Any issue that warrants interrupting normal sprint work
DO NOT Use For
- Minor bugs (use normal bug process)
- Features that didn't make the last release
- Polish items
Steps
1. Triage — Is This a Hotfix?
Confirm:
- Severity: Is this truly S0 or S1?
- Impact: How many users affected?
- Urgency: Can this wait for next scheduled release?
- Workaround: Is there a temporary workaround players can use?
If answer to "can this wait" is "yes" → not a hotfix. Use normal process.
2. Diagnose Fast
- Reproduce the issue (fast repro is critical)
- Identify root cause (not just symptom)
- Identify affected files/systems
- Delegate to the most relevant specialist for root-cause analysis
3. Design Minimal Fix
The fix should be:
- Minimal: Smallest possible change to fix the issue
- Targeted: Only touch files related to the bug
- Reversible: Easy to revert if the fix causes new issues
- Tested: Verify it fixes the issue without breaking neighbors
DO NOT:
- Bundle unrelated improvements
- Refactor around the bug
- Add new features
- Make "while we're here" changes
4. Test the Fix
- Reproduce the original issue → verify fix works
- Test neighboring functionality → verify no regression
- Test common user flows → verify no side effects
- If possible, test in a private place first
5. Expedited Review
- Quick code review (via lead-programmer or technical-director)
- Minimum checks: no hardcoded values, no client-trust, no new security holes
- If diff is < 20 lines, review should be < 10 minutes
6. Publish
- Publish directly to production place (skip staging if urgent)
- Use feature flag to enable fix if possible (instant rollback path)
- Communicate immediately via community channels
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 · 120 lines · 32 tokens per session scan A c46847b64572
hotfix is a skill published in the GitHub repository CodePhobiia/claude-roblox-game-studio (15 stars, last pushed 6mo ago), licensed MIT. It adds 32 tokens to every session and 897 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-08-31.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
deck-retro
Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs. Use when a user wants to find recurring failures or take their own finding from investigation through synthetic reproduction, a user-filed issue, a test-first fix and contributor PR handoff. Also use for weekly usage…
cwv-optimizer
Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…
incident-response-incident-response
Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.