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 skills/danielvm-git/bigpowers/quick-fixnpx skills add danielvm-git/bigpowers --skill quick-fixgit clone --depth 1 https://github.com/danielvm-git/bigpowersWhat 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.00054 | $0.01169 |
| Opus 5 | $0.00027 | $0.00584 |
| Sonnet 5 | $0.00011 | $0.00234 |
| Haiku 4.5 | $0.00005 | $0.00117 |
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 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.
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 — 115 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.
- 2d ago First seen · 115 lines · 54 tokens per session scan A 08fc1f677509
quick-fix is a skill published in the GitHub repository danielvm-git/bigpowers (156 stars, last pushed 25d ago), licensed MIT. It adds 54 tokens to every session and 1,169 once invoked, about $0.0003 per session on Opus 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-08-30.
Other skills, from other repositories
shared/tech-stack-detection
检测项目技术栈的通用方法，通过分析配置文件识别语言、框架、工具链.
devops/changelog-generation
自动生成 CHANGELOG，基于 git 提交历史和 pipeline 产物信息，遵循 Conventional Commits 和 Keep a Changelog 规范.
boss
可审计的 agent 团队：BMAD 全自动研发流水线编排器。编排 9 个专业 Agent（PM、架构师、UI Designer、Tech Lead、Scrum Master、Frontend、Backend、QA、DevOps）从需求到部署，每一步都有事件溯源 + 不可绕过门禁 + 确定性 eval——可验证测试真跑、门禁真过。支持单环节切片命令（/boss:plan /review /qa /ship）与无 CLI 纯 Markdown 降级。 Triggers: 'boss mode', '/boss', '全自动开发', '从需求到部署', '帮我做一个', 'build this', 'ship it', '全流程'…
debloat
Compress an artifact that has accreted into bloat — padding, over-qualification, fused sentences, walls of enumeration, adjacent restatement — down to its load-bearing density, meaning preserved. Use when prose is correct and current but has grown verbose or patched-over and you want it tight without a full rewrite.
bmad-dev-story
Execute story implementation following a context filled story spec file. Use when the user says "dev this story [story file]" or "implement the next story in the sprint plan".
bmad-validate-prd
Validate a PRD against standards. Use when the user says "validate this PRD" or "run PRD validation".