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 commands/christopherlouet/claude-base/ops-hotfixgit clone --depth 1 https://github.com/christopherlouet/claude-baseWrote 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/christopherlouet/claude-base/ops-hotfix)<a href="https://agentmods.dev/commands/christopherlouet/claude-base/ops-hotfix"><img src="https://agentmods.dev/badge/commands/christopherlouet/claude-base/ops-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.00308 |
| Opus 5 | $0.00000 | $0.00154 |
| Sonnet 5 | $0.00000 | $0.00062 |
| Haiku 4.5 | $0.00000 | $0.00031 |
Grade A, and why
ops-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 2d 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.
What it actually says
HOTFIX Agent
Workflow for urgent production fixes.
Request context
$ARGUMENTS
Objective
Guide the quick and secure fix of a production bug, with incident classification, minimal fix, and post-mortem.
Workflow
- Classify the incident (P0 critical, P1 high, P2 medium, P3 low)
- Assess urgency (user impact, workaround, rollback possible)
- Create the hotfix branch from main/production
- Diagnose quickly (logs, monitoring, code)
- Apply the minimal fix (ONLY the immediate problem)
- Validate with critical tests and smoke test
- Create the PR with hotfix label and reference to the issue
- Post-mortem: document, identify improvements, merge into develop
Expected output
- Classification of the incident with severity
- Hotfix branch created with minimal fix
- Commit with reference to the issue and root cause
- Post-mortem checklist
Related agents
| Agent | Usage |
|---|---|
/dev:dev-debug |
Diagnose the problem |
/ops:ops-release |
Release after hotfix |
/ops:ops-monitoring |
Verify post-deployment |
IMPORTANT: Speed AND safety. Do not sacrifice safety for speed.
IMPORTANT: One hotfix = ONE problem. No "while we're at it".
YOU MUST test the hotfix before prod deployment.
NEVER deploy a hotfix without rollback capability.
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.
- 2d ago First seen · 48 lines · 0 tokens per session scan A 0e0c664942a2
ops-hotfix is a command published in the GitHub repository christopherlouet/claude-base (5 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 308 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-03.
Other commands, from other repositories
close
End session with verification, commits, and documentation.
hotfix
紧急修复快速通道，跳过 PM/Lead 直接 Dev→Verify→Commit.
audit-fix
Run audit, prioritize findings, auto-fix via quick tasks, test, and commit.
github
(dev-only) github maintainer harness — GitHub issue-fix and PR-review via gh CLI. NOT distributed to user projects.
loop
Iteratively fix issues until all resolved or max iterations reached.
sync
Synchronize documentation, codemaps, and create pull request.