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 skills add richardcb/oh-my-gemini --skill quick-fixgit clone --depth 1 https://github.com/richardcb/oh-my-geminiWrote 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/skills/richardcb/oh-my-gemini/quick-fix)<a href="https://agentmods.dev/skills/richardcb/oh-my-gemini/quick-fix"><img src="https://agentmods.dev/badge/skills/richardcb/oh-my-gemini/quick-fix.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.1 | $0.00055 | $0.00876 |
| Opus 5 | $0.00028 | $0.00438 |
| Sonnet 5 | $0.00011 | $0.00175 |
| Haiku 4.5 | $0.00006 | $0.00088 |
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 8d 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quick Fix Skill
Goal
Fix a specific bug or issue with the smallest correct change. This skill prioritizes speed and precision over comprehensive refactoring.
Activation Triggers
- User says "quick fix", "small fix", "patch", "hotfix", or "just fix this"
- User reports a specific, isolated bug
- User wants a targeted change without broader planning
- Error messages or failing tests that need a direct fix
When NOT to Use
This skill is explicitly not a planning workflow. If the fix requires:
- Changing more than 3 files
- Architectural decisions
- New features or capabilities
- Extensive refactoring
Then use the technical-planning or refactor skill instead.
Process
1. Understand the Bug
Get a clear description of the problem:
Questions to ask (if not already clear):
- What is the expected behavior?
- What is the actual behavior?
- Can you share the error message or reproduction steps?
# Check for recent errors
git log --oneline -5 2>/dev/null
# Check test failures if applicable
npm test 2>&1 | tail -20 || echo "No test command"
2. Locate the Code
Find the relevant file(s) quickly:
# Search for error-related code
grep -rn "errorKeyword" src/ --include="*.ts" --include="*.js" | head -15
# Find the function or component
grep -rn "functionName" src/ --include="*.ts" --include="*.js" | head -10
Read the file and understand the immediate context around the bug.
3. Apply Minimal Fix
Make the smallest correct change:
Fix principles:
- Change only what is necessary to fix the bug
- Do not refactor surrounding code
- Do not add features
- Do not change formatting of untouched code
- Preserve existing patterns and conventions
Common fix patterns:
| Bug Type | Fix Pattern |
|---|---|
| Null/undefined | Add null check or optional chaining |
| Type mismatch | Fix type or add type guard |
| Off-by-one | Correct boundary condition |
| Missing await | Add await keyword |
| Wrong condition | Fix boolean logic |
| Missing import | Add the import statement |
| Stale state | Fix dependency array or use functional update |
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.
- 8d ago First seen · 134 lines · 55 tokens per session scan A 25d10ad59801
quick-fix is a skill published in the GitHub repository richardcb/oh-my-gemini (16 stars, last pushed 5mo ago), licensed MIT. It adds 55 tokens to every session and 876 once invoked, about $0.0003 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-30.
Other skills, from other repositories
canary-watch
Post-deploy monitoring and canary health verification.
benchmark
Performance baseline measurement and regression detection.
troubleshooter
Specialized in system-wide troubleshooting using metrics and logs.
click-path-audit
Trace every user-facing button/touchpoint through its full state change sequence to find bugs where functions individually work but cancel each other out, produce wrong final state, or leave the UI in an inconsistent state. Use when: systematic debugging found no bugs but users report broken buttons, or after any…
plankton-code-quality
Write-time code quality enforcement using Plankton — auto-formatting, linting, and AI-powered fixes on every file edit via hooks.
evm-token-decimals
Prevent silent decimal mismatch bugs across EVM chains. Covers runtime decimal lookup, chain-aware caching, bridged-token precision drift, and safe normalization for bots, dashboards, and DeFi tools.