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.
git clone --depth 1 https://github.com/fatihkan/badiWrote 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/commands/fatihkan/badi/hotfix)<a href="https://agentmods.dev/commands/fatihkan/badi/hotfix"><img src="https://agentmods.dev/badge/commands/fatihkan/badi/hotfix.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.1 | $0.00000 | $0.00866 |
| Opus 5 | $0.00000 | $0.00433 |
| Sonnet 5 | $0.00000 | $0.00173 |
| Haiku 4.5 | $0.00000 | $0.00087 |
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 today.
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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Emergency fix workflow. Manages a fast, safe patching process for production errors.
Required Tools
- Bash (git operations, running tests)
- Read (error logs, stack trace analysis)
- Write (fix files)
- Grep (error source detection)
- Glob (related file scan)
- Agent (auditor: fast T1 audit)
Scope Protection
IMPORTANT: This workflow is for emergency fixes only. Scope creep is strictly rejected. If another improvement opportunity appears during the fix, record it as a note but continue WITHOUT applying it.
Step 1: Create the Hotfix Branch
1a: Check the Current State
- Verify a clean working directory with
git status - Stash uncommitted changes if any
1b: Create the Branch
- Detect the main branch:
mainormaster - Create it with
git checkout -b hotfix/[short-description] [main-branch] - Branch naming: descriptive names like
hotfix/fix-login-crash,hotfix/patch-api-timeout
Step 2: Isolate the Bug
2a: Gather the Error Info
- Ask the user for the error log or stack trace
- Read the bug report if one exists
- Determine the reproduction conditions
2b: Source Detection
- Follow the files and line numbers in the stack trace
- Grep the error message across the codebase
- Check when the bug first appeared via git log
- Suggest
git bisect(if needed)
2c: Impact Analysis
- Identify the modules affected by the bug
- Check the current state of the related tests
Step 3: Apply the Minimal Fix
3a: Scope Check
- The fix must target only the bug's root cause
- NO refactoring
- NO new features
- NO touching unrelated code
- For every change ask: "Is this change essential to fixing the bug?"
3b: Write the Fix
- Make the smallest possible change
- Add a comment explaining why the change was made
- Minimize side effects
Step 4: Run the Targeted Tests
4a: Run the Existing Tests
- Run the tests of the module the bug relates to
- Run the whole related test suite as a regression check
- Report the test results
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.
- today First seen · 128 lines · 0 tokens per session scan A bb8f5c93692a
hotfix is a command published in the GitHub repository fatihkan/badi (7 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 866 tokens. 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-06.
Other commands, from other repositories
plan-execute
Execute a validated plan: worktree isolation, TDD scaffolding, level-based parallel agents, quality gate with smoke test, PR creation and merge. Handles everything through to merged PR.
catchup
Restore context after /clear by summarizing recent work and project state.
commit
Generate a conventional commit message for staged changes.
check-cache-bugs
Audit Claude Code setup for cache bugs (CC#40524) — sentinel, --resume/--continue, attribution header + ArkNill B3/B4/B5.
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary — the complete landing pipeline.
investigate
Systematic root-cause debugging — find the cause before writing any fix.