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/srstomp/pokayokay/hotfixgit clone --depth 1 https://github.com/srstomp/pokayokayWrote 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/srstomp/pokayokay/hotfix)<a href="https://agentmods.dev/commands/srstomp/pokayokay/hotfix"><img src="https://agentmods.dev/badge/commands/srstomp/pokayokay/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 | $0.00007 | $0.01153 |
| Opus 5 | $0.00003 | $0.00576 |
| Sonnet 5 | $0.00001 | $0.00231 |
| Haiku 4.5 | $0.00001 | $0.00115 |
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 3d 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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hotfix Workflow
Production incident: $ARGUMENTS
Hotfix Philosophy
- Mitigate first: Stop the bleeding before fixing root cause
- Communicate: Keep stakeholders informed
- Fix safely: Avoid making things worse
- Learn: Postmortem prevents recurrence
Steps
1. Triage Severity
| Severity | Impact | Response |
|---|---|---|
| P0 | Service down, data loss | Drop everything |
| P1 | Major feature broken | Urgent, today |
| P2 | Minor issue, workaround exists | Soon, this week |
2. Create Hotfix Task
npx @stevestomp/ohno-cli create "HOTFIX: $ARGUMENTS" -t bug -p P0
npx @stevestomp/ohno-cli start <task-id>
3. Investigate Impact
- Who/what is affected?
- When did it start?
- Is it getting worse?
- What changed recently?
4. Mitigate (if possible)
Quick actions to reduce impact:
- Feature flag disable
- Rollback deployment
- Scale up resources
- Database fix
- Redirect/workaround
Document mitigation taken:
## Mitigation Applied
[What was done to reduce impact]
5. Root Cause Analysis
Quick investigation:
- What changed recently?
- What's in the error logs?
- Can we reproduce in staging?
6. Dispatch Agent Pipeline
Do not implement the fix inline. Hand off to the agent pipeline.
Read and follow skills/work-session/references/bug-fix-pipeline.md with these settings:
- Mode:
/hotfix(max 2 fixer retries, max 1 review cycle, Critical-only quality threshold) - Root cause: from Step 5
- Impact analysis: from Step 3
- Mitigation applied: from Step 4 (if any)
The pipeline will:
- Dispatch
yokay-implementerwith hotfix context + mandatory regression test - Auto-fix test failures if needed (
yokay-fixer, max 2 attempts) - Verify regression test exists (re-dispatch if missing)
- Run two-stage review (
yokay-spec-reviewer+yokay-quality-reviewer, Critical-only mode)
Time pressure handling:
- Fixer gets 2 attempts (not 3)
- Review cycle limit is 1 — first failure escalates to human immediately
- Review only fails on Critical severity (security, crash, data loss)
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.
- 3d ago First seen · 174 lines · 7 tokens per session scan A cb0b21c60431
hotfix is a command published in the GitHub repository srstomp/pokayokay (9 stars, last pushed 2mo ago), licensed MIT. It adds 7 tokens to every session and 1,153 once invoked, about $0.0000 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-08-31.
Other commands, from other repositories
README
Git workflow and quality assurance commands for the claude-skills repository.
minutes-ideas
Surface recent voice memos and ideas captured from any device. Use when the user asks "what ideas did I have?", "what were my recent memos?", "what did I record while walking?", or wants to recall a captured thought.
engage.actions
Execute Phase 7 - Actions on Objectives and Goal Achievement.
sync-linear
Sync current work with Linear ticket status.
version
Show installed vs latest ai-sdlc plugin version. Bypasses the 24h SessionStart cache.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.