Borrowing it
Nothing to install: this file belongs to robconery/kolea. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/robconery/kolea/main/.claude/commands/quick-fix.mdgit clone --depth 1 https://github.com/robconery/koleaWrote 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/robconery/kolea/quick-fix)<a href="https://agentmods.dev/commands/robconery/kolea/quick-fix"><img src="https://agentmods.dev/badge/commands/robconery/kolea/quick-fix/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/robconery/kolea/quick-fix"><img src="https://agentmods.dev/badge/commands/robconery/kolea/quick-fix.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.00021 | $0.00678 |
| Opus 5.5 | $0.00008 | $0.00271 |
| Sonnet 5.5 | $0.00004 | $0.00136 |
| Haiku 4.5 | $0.00002 | $0.00068 |
Grade A, and why
quick-fix 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 2mo 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
quick-fix
For the trivial stuff: a typo, a reversed condition, a dead try/catch, a
misnamed variable, a stray import. The kind of bug where opening
/explore → /design → /plan → /build-loop would be absurd.
Scope
- IN: one-spot fixes that a competent engineer would commit straight to
mainwithout ceremony. Single concern. Usually < ~20 lines changed. - OUT: anything that needs a design call, touches a public API contract,
changes behavior across modules, or needs new tests beyond what already
exists. If it smells like that, stop and suggest
/planor/build-loop.
Argument
$ARGUMENTS describes the fix in the user's words (e.g. "remove the
unneeded try/catch in fetchUser", "fix the typo in the login button").
If empty, ask one short clarifying question.
Loop
- Locate. Find the exact site. If the description is ambiguous or matches multiple places, ask before guessing.
- Confirm it's actually small. If reading the surrounding code reveals
the fix is non-trivial (touches a class boundary, changes a contract,
needs new branches of test coverage), stop and escalate — tell the
user this isn't a quick-fix and suggest
/plan. - Consult skills selectively. Only load a code-quality skill if the
fix genuinely touches its territory:
solid-principles/design-principles/gof-patterns: only if the fix sits at a class or module boundary, or changes a control-flow pattern. Skip for typos, comments, log strings, dead code removal.agent-teams: skip — quick-fixes are single-threaded by definition.typescript-best-practices: consult if the fix involves types,any/unknown, null handling, or error shape.
- Apply the edit. Use
Edit, notWrite. Match surrounding style. - Verify. Run the project's typecheck and tests if they're fast. If
they're slow or absent, run the narrowest check that proves the fix
(e.g.
tsc --noEmiton the file, or the single related test). - Report and ask before committing. Show the diff summary and propose
a one-line commit message. Do not commit unless the user says go —
committing straight to
mainis a shared-state action.
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.
- 2mo ago First seen · 63 lines · 21 tokens per session scan A ecebfd994975
quick-fix is a command published in the GitHub repository robconery/kolea (11 stars, last pushed 28d ago), licensed MIT. It adds 21 tokens to every session and 678 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
install-lint-stack
Bootstrap industry-leading lint+autofix+commit-hygiene stack on the current project. Drops in lefthook, oxlint, ESLint, Prettier, Stylelint, markdownlint, ruff, shellcheck, shfmt, yamllint, hadolint, actionlint, jscpd, knip, semgrep, gitleaks, commitizen + git-cz-emoji (emoji-mandatory commits), and semantic-release.…
improve-lint
Run the AI-augmented lint self-improvement loop on the current project. Scans .lint-history/ for recurring violation patterns (≥3 hits in 30d window), drafts a Claude-ready prompt to author a new semgrep rule for the top candidate, and surfaces the proposal under .lint-history/proposals/ .md. Non-blocking analysis.…
drift-check
Run the drift-detection checklist (incl. agent-drift signals); report + fix in-turn.
plan-execute-verify-repair
Run the autonomous-engineering operating loop on a task (plan→implement→verify→repair→report).
harness-check
Validate harness invariants — CLAUDE↔AGENTS symlink, sub-agent frontmatter, Kimi roster symlink, hook wiring, workflows.
bottleneck-detect
Analyze performance bottlenecks in swarm operations and suggest optimizations.