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 cenconq25/claude-code-app-studio --skill hotfixgit clone --depth 1 https://github.com/cenconq25/claude-code-app-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/cenconq25/claude-code-app-studio/hotfix)<a href="https://agentmods.dev/skills/cenconq25/claude-code-app-studio/hotfix"><img src="https://agentmods.dev/badge/skills/cenconq25/claude-code-app-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/cenconq25/claude-code-app-studio/hotfix"><img src="https://agentmods.dev/badge/skills/cenconq25/claude-code-app-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.00057 | $0.01925 |
| Opus 5 | $0.00028 | $0.00962 |
| Sonnet 5 | $0.00011 | $0.00385 |
| Haiku 4.5 | $0.00006 | $0.00193 |
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 5d 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 — 276 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hotfix
The break-glass procedure for shipping a fix outside a sprint. Trades process for speed but keeps an audit trail tight enough to survive post-incident review.
Phase 1: Confirm This Is Actually a Hotfix
Hotfix is justified only when ALL of these hold:
- A production build is currently live and impacted.
- The issue is S1 OR a store-rejection blocker OR a security exposure.
- Waiting for the next sprint would cause further user harm.
Otherwise, route to /bug-triage for normal scheduling.
Ask the user via AskUserQuestion to confirm the trigger:
[A] Live S1 — users impacted right now[B] App Store / Play Store rejection — review board needs a fix[C] Security disclosure — needs immediate patch[D] Cancel — this is not a hotfix
If [D], stop and recommend /bug-report or /bug-triage.
Phase 2: Resolve the Bug Record
If BUG-ID is given, read production/qa/bugs/BUG-[ID]-*.md. If not,
prompt the user to file one via /bug-report first — every hotfix must
have a tracked bug.
Read:
- The bug record in full.
- Any related ADRs from the bug's "Related" section.
- The most recently shipped build's tag (via
git tag --sort=-creatordate).
Phase 3: Approval Gate
Hotfix bypasses sprint planning, so a higher approval bar applies. Use AskUserQuestion to capture each:
- Engineering Lead approval (name)
- Producer approval (name)
- QA Lead approval (name)
- Release Manager approval (name)
If any approval is missing, stop. The audit trail requires all four for a true hotfix. (The user can choose to proceed without a formal hotfix process — but then it's a normal sprint fix.)
Record approvals into the hotfix log (created in Phase 8).
Phase 4: Branch Strategy
Determine the source. Use Bash:
git fetch --tags
git tag --sort=-creatordate | head -n 5
Confirm with the user which release tag is currently live in production.
Create the hotfix branch from that tag:
git checkout -b hotfix/BUG-[ID]-[short-slug] [release-tag]
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.
- 5d ago First seen · 276 lines · 57 tokens per session scan A e852608ce710
hotfix is a skill published in the GitHub repository cenconq25/claude-code-app-studio (40 stars, last pushed 4mo ago), licensed MIT. It adds 57 tokens to every session and 1,925 once invoked, about $0.0003 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 skills, from other repositories
git-advanced-workflows
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
gsd-audit-fix
Autonomous audit-to-fix pipeline — find issues, classify, fix, test, commit.
git-worktree-precommit-hook-flutter-failure
Fix git pre-commit hook failures in Flutter projects when using git worktrees. Use when: (1) Pre-commit hook with flutter analyze fails during git commit but passes when run manually, (2) Hook output shows "Resolving dependencies..." then immediately fails with no actual analysis errors, (3) Working in a git worktree…
git-mastery
Advanced Git: rebase, bisect, reflog, cherry-pick, worktrees, LFS. Triggers: rebase, bisect, cherry-pick, reflog, force push, merge conflict, worktree.
magpie-setup-upstream-fix
Turn a framework bug or quirk the agent hit while running a Magpie skill or tool into a fix PR against apache/magpie — one PR per issue. First confirms the problem is a framework defect (not a local misconfiguration or a stale snapshot), then searches apache/magpie for an existing issue or PR that already covers it…
stage-payload-reverts
Create TRT JIRA bugs, open revert PRs, and trigger payload jobs for high-confidence revert candidates.