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/lugassawan/swe-workbenchWrote 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/lugassawan/swe-workbench/hotfix)<a href="https://agentmods.dev/commands/lugassawan/swe-workbench/hotfix"><img src="https://agentmods.dev/badge/commands/lugassawan/swe-workbench/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/commands/lugassawan/swe-workbench/hotfix"><img src="https://agentmods.dev/badge/commands/lugassawan/swe-workbench/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.00707 |
| Opus 5.5 | $0.00013 | $0.00283 |
| Sonnet 5.5 | $0.00006 | $0.00141 |
| Haiku 4.5 | $0.00003 | $0.00071 |
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 20d 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 request: $ARGUMENTS
If $ARGUMENTS contains a ticket reference, invoke swe-workbench:ticket-context first and prepend its structured summary to the delegation context below. Skip if $ARGUMENTS is free-text with no recognizable ref. (Trigger patterns are defined in that skill's "When to invoke" section.)
Interrogation mode. Before producing anything, resolve the mode:
- Explicit signal in the invocation is honored without asking. grill-me =
--grill, "grill me", or "grill-me mode". standard =--standard, "standard", or "quick". Strip the signal from $ARGUMENTS and record the resolved mode. - No explicit signal: ask via
AskUserQuestion— one question, header "Mode", options Standard (recommended, listed first) and Grill me. Standard description: "Lightweight clarify — a restatement and at most one question, then proceed." Grill-me description: "Relentlessly walk the decision tree one question at a time, each with a recommended answer, self-answering from the codebase where possible." Use the user's choice.
Standard mode: proceed with the command's existing lightweight clarify (a restatement and at most one clarifying question) — do not ask the mode question again.
Grill-me mode: activate swe-workbench:workflow-grill and run its interrogation loop to completion (exit on shared understanding or when the user says "proceed"). Then thread the emitted ## Resolved decisions block into the command's normal artifact/delegation step below — the same way a ticket-context summary is prepended — and continue as in standard mode.
Activate the swe-workbench:workflow-hotfix skill. It owns the reordered lifecycle — a plain branch (never a worktree), a minimal fix with TDD relaxed, a ready-for-review PR opened before verification and review, then verify + review running against the open PR, then a reconcile step that strips the deferred-verification marker only if the regression test was backfilled and verification is green.
Absolute rules:
- Always branch, never worktree —
git checkout -b hotfix/<slug>off the synced default branch. This command exists specifically to skip worktree ceremony. - Always open the PR ready-for-review, never draft — speed is the point.
- Verification and review always run after the PR is opened, never before — this command's entire identity is deferred verification. Do not reorder to verify-then-PR; that is
/swe-workbench:implement. - Write the deferred-verification marker (
<!-- swe-workbench:deferred-verification -->) into the PR body at open time. Strip it only if the regression test is backfilled AND verification is green, before requesting merge — never strip it preemptively. - If the ticket lacks acceptance criteria, stop and ask the user — do not invent scope, even under time pressure.
- Do not invent architectural answers — escalate any genuine design fork to
swe-workbench:senior-engineer.
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.
- 20d ago Changed · +2 lines d381870b6606
- 1mo ago First seen · 28 lines · 32 tokens per session scan A a3a418e80460
hotfix is a command published in the GitHub repository lugassawan/swe-workbench (3 stars, last pushed 2d ago), licensed MIT. It adds 32 tokens to every session and 707 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 commands, from other repositories
review
Fast review of staged changes. Critical findings only — no style nits.
pre-push
Run the full review skill on all changes since last push.
release
Release manager for frontend and mobile. Writes App Store notes, user-facing changelog, flags stale docs and landing copy. Actions: notes | changelog | docs | sync.
status
The state of play, computed fresh: branch, dirty files, the active sprint, open work, index freshness.
worktree
Manage git worktrees for isolated feature development.
code-review
Review the current branch changes for bugs and style issues.