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/danielvm-git/bigpowersWrote 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/rules/danielvm-git/bigpowers/quick-fix)<a href="https://agentmods.dev/rules/danielvm-git/bigpowers/quick-fix"><img src="https://agentmods.dev/badge/rules/danielvm-git/bigpowers/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/rules/danielvm-git/bigpowers/quick-fix"><img src="https://agentmods.dev/badge/rules/danielvm-git/bigpowers/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.00050 | $0.01163 |
| Opus 5.5 | $0.00020 | $0.00465 |
| Sonnet 5.5 | $0.00010 | $0.00233 |
| Haiku 4.5 | $0.00005 | $0.00116 |
Grade A, and why
quick-fix scanned grade A with 1 finding 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 1mo 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
5. **Verifiable with a single assertion** — one test, one curl, one grep can prove it works How it starts
The opening of the file, as written. The whole thing — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quick Fix
HARD GATE — ALL entry criteria must pass before invoking quick-fix. If any guardrail triggers during execution, abort immediately and fall back to
investigate-bug. Do NOT use quick-fix for logic changes, multi-file edits, or diffs > 5 lines.
Fast-track for trivial data-only fixes that do not require the full bug-fix chain.
When a bug fix is purely data — an add-missing-key, a typo correction, a config value update — the standard 6-skill chain (investigate-bug → diagnose-root → develop-tdd → kickoff-branch → verify-work → release-branch) is wasteful overhead. Quick-fix collapses it to 2 skills: quick-fix then release-branch.
Discovered gate failures (e51s04)
A Preflight, golden suite, or baseline red failure discovered during unrelated work is valid quick-fix entry when the root cause is a data-only gap (missing key, typo, stale config) — no user-reported bug required. If guardrails abort (logic change, >1 file, >5 lines), fall back to fix-bug instead of narrating and continuing.
Entry Criteria (ALL must be true)
Before invoking quick-fix, evaluate every item in this checklist:
- Purely data change — adding a missing key, fixing a typo, updating a config value, correcting a constant
- No logic change — no function signature, condition, loop, or control flow is modified
- No refactor risk — the change does not reorganize or rename existing structures
- No API surface change — no exported symbol, interface, or contract changes
- Verifiable with a single assertion — one test, one curl, one grep can prove it works
- Affects ≤ 1 file
- Affects ≤ 5 lines changed
Guardrails (HARD ABORT — all must pass)
If ANY guardrail triggers, abort immediately and suggest investigate-bug instead:
| Guardrail | Check |
|---|---|
| >1 file | The fix touches more than one file |
| >5 lines | The diff exceeds 5 lines |
| Logic change | Any function signature, condition, or loop is modified |
| Complex verify | The verify command is more than one pipeline |
| Test breakage | Running npm test or equivalent breaks any existing test |
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.
- 1mo ago First seen · 114 lines · 50 tokens per session scan A 8077be55131e
quick-fix is a cursor rule published in the GitHub repository danielvm-git/bigpowers (267 stars, last pushed 27d ago), licensed MIT. It adds 50 tokens to every session and 1,163 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other cursor rules, from other repositories
RULE
Network troubleshooting — systematic diagnosis and resolution for connectivity, DNS, proxy, SSL, HTTP errors.
gemini-precision
High-precision engineering and execution guardrails optimized for Google Gemini models. Enforces zero-assumption file inspection, complete non-lazy implementations, surgical blast-radius containment, and mandatory proof-of-work execution.
debugging
Debugging discipline. Apply when investigating a bug, test failure, or unexpected behavior.
bug-fix-tdd-guard
A rule for fixing software bugs with test-driven development, or TDD: first reproduce the bug, then write a test that fails, then make the smallest code change that passes it, and finally run the full checks.
ai-mcp-development
Rule Name: ai-mcp-development Description: Guidelines for developing and debugging MCP servers and tools. Filters.
performance
Performance: profiling-first optimization, caching, bottleneck patterns.