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/rshade/mcp-devtools-server/quick-fixgit clone --depth 1 https://github.com/rshade/mcp-devtools-serverWhat 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.00452 |
| Opus 5 | $0.00000 | $0.00226 |
| Sonnet 5 | $0.00000 | $0.00090 |
| Haiku 4.5 | $0.00000 | $0.00045 |
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.
What it actually says
Launch Quick Fix Agent (Haiku) for fast bug fixes and minor improvements.
Usage: /quick-fix [issue-number]
Best for:
- Simple bug fixes (<1 hour)
- Linting errors
- Test failures
- Documentation fixes
- Minor refactoring
Example: /quick-fix 145
Launch Quick Fix Agent with Haiku model for efficient fixes.
Use the Task tool with:
- subagent_type: general-purpose
- model: haiku
- prompt: Quick fix implementation
Task:
You are the Quick Fix Agent. Implement fast fixes for issue #{{ISSUE_NUMBER}}.
Workflow:
-
Read issue (2-3 min):
gh issue view {{ISSUE_NUMBER}} --repo rshade/mcp-devtools-server --json title,body,labels -
Analyze scope (5 min):
- Is this truly quick (<1 hour)?
- What files need changing?
- What tests are needed?
- If complex, recommend full implementation agent instead
-
Implement fix (20-30 min):
- Read affected files
- Make targeted changes (Edit tool)
- Add/update tests
- Follow project patterns (CLAUDE.md)
-
Validate (10 min):
make lint # Must pass make test # Must pass make build # Must pass -
Generate commit:
fix(component): brief description - Fix specific issue - Add test coverage Fixes #{{ISSUE_NUMBER}}
Quick Fix Checklist:
- Fix is <50 lines changed
- Tests added/updated
- All quality gates pass
- Follows project conventions
- Commit message follows conventional format
If issue is complex: Return: "This issue requires full implementation. Use /implement-python-tool or manual development."
Success criteria:
- Fix implemented in <1 hour
- Quality gates pass
- Ready for PR
Return summary with files changed and commit message.
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 · 79 lines · 0 tokens per session scan A ac6793d8c54b
quick-fix is a command published in the GitHub repository rshade/mcp-devtools-server (5 stars, last pushed 3d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 452 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
paul:help
Show available PAUL commands and usage guide.
brooks-audit
Run a Brooks-Lint architecture audit.
paul:verify
Guide manual user acceptance testing of recently built features.
kill-mutants
Analyze surviving mutants from a mutation testing run and write targeted unit tests to kill them. Re-runs mutations to confirm kills.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
mutate
Run mutation testing to verify test quality. Builds a custom mutation tool or uses an existing framework, runs mutations, and reports the mutation score with surviving mutants.