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/pablomarin/claude-codex-forge/quick-fixgit clone --depth 1 https://github.com/pablomarin/claude-codex-forgeWhat 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.00000 | $0.00793 |
| Opus 5 | $0.00000 | $0.00396 |
| Sonnet 5 | $0.00000 | $0.00159 |
| Haiku 4.5 | $0.00000 | $0.00079 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quick Fix Workflow
For trivial changes only. If in doubt, use
/new-featureor/fix-buginstead.
When to Use This
- Typo fixes
- Comment updates
- Single-line bug fixes with obvious cause
- Config tweaks
- Documentation-only changes
- Changes touching fewer than 3 files
- No architectural impact
If ANY of these apply, use the full workflow instead:
- You're not 100% sure of the fix
- Multiple files need changes
- The fix involves business logic
- Tests need to be added/modified
- Database/API changes involved
- User-facing behavior changed — UI, API response, CLI output, navigation, permissions. Quick-fix skips E2E verification; any user-facing change requires the
verify-e2eagent via/fix-bug. Trivial = no behavior change (typos, comments, dead code removal, internal refactors that preserve behavior).
Pre-Flight Check
- Verify branch: You must NOT be on
main. If on main:git checkout -b "fix/$ARGUMENTS"
Research Check
Quick fixes skip the full research-first agent. However, if this change touches an external dependency or API (version bump, API call change, new library import):
- Check the library's current docs via Context7 or WebSearch before implementing
- Verify no breaking changes between your version and the one you're targeting
If purely internal (typo fix, config change, style cleanup): no research needed.
The Fix
- Make the change
- Verify it works (run relevant tests or check manually)
Quality Gates (STILL REQUIRED)
Verify (USE SUBAGENT - saves context window)
MUST use the verify-app subagent - Do NOT run tests yourself.
Using a subagent keeps test output out of your context window, preserving tokens for actual work.
Invoke the subagent:
Use the Task tool with:
- subagent_type: "verify-app"
- prompt: "Run verification on current changes and report pass/fail verdict."
Note: Quick-fix doesn't create worktrees. For parallel development, use
/new-featureor/fix-buginstead.
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 · 130 lines · 0 tokens per session scan A 50a183b8186b
quick-fix is a command published in the GitHub repository pablomarin/claude-codex-forge (5 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 793 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-08-31.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.