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/fix-bugnpx skills add danielvm-git/bigpowers --skill fix-buggit 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.00044 | $0.00753 |
| Opus 5 | $0.00022 | $0.00377 |
| Sonnet 5 | $0.00009 | $0.00151 |
| Haiku 4.5 | $0.00004 | $0.00075 |
Grade A, and why
fix-bug 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fix Bug
Boundary: Orchestrator flow — chains investigate-bug (entry point + RCA via diagnose-root) → develop-tdd → validate-fix. Does not implement RCA or write bug files directly.
Orchestrates fix_bug flow without mixing epic build state.
HARD GATE — Set
specs/state.yamlactive_flow: fix_bugandbug_cycle.current_step: 1before starting.
Discovered gate failures (e51s04)
Valid entry without a user-reported bug when:
- Preflight or CI is red at kickoff or verify-work
- Golden suite or project baseline is red (
bash scripts/run-verification-gates.shor equivalent) - A reproducible gate failure during unrelated epic work exceeds quick-fix guardrails
Create specs/bugs/BUG-*.md via investigate-bug (or inline in fix-bug step 1) describing the gate failure, then run the standard fix_bug chain.
Five steps (bug_cycle in state.yaml)
| Step | Skill / action |
|---|---|
| 1 | investigate-bug — create BUG-*.md with RCA |
| 2 | diagnose-root — 4-phase root cause analysis |
| 3 | develop-tdd — red-green against bug file verify steps |
| 4 | validate-fix — re-run failing test, full suite, lint |
| 5 | release-branch — PR or solo land the fix |
Checkpoint / resume
Track progress via specs/state.yaml bug_cycle:
bug_cycle.current_step: current step (1–5)bug_cycle.completed_steps: completed step numbershandoff.next_skill: skill for the current step- On resume, read
bug_cycle.current_stepand continue from there
Process
- Step 1 — investigate-bug: If no
specs/bugs/BUG-*.md, runinvestigate-bugfirst — it handles history check, RCA (viadiagnose-root), fix approach, and writes the bug file. Incrementbug_cycle.current_stepto 2 on completion. - Step 2 — diagnose-root: Run 4-phase RCA (reproduce → isolate → hypothesize → verify). Record findings in the bug file. Increment to step 3.
- Step 3 — develop-tdd:
develop-tddagainst the bug file's verify steps. Increment to step 4 on all-green. - Step 4 — validate-fix:
validate-fix— re-run failing test, full suite, typecheck, lint. Increment to step 5. - Step 5 — release-branch: Land the fix via
release-branch. Clearbug_cycleandactive_flowwhen done.
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 · 68 lines · 44 tokens per session scan A 8f8b5dc48c02
fix-bug is a skill published in the GitHub repository danielvm-git/bigpowers (156 stars, last pushed 25d ago), licensed MIT. It adds 44 tokens to every session and 753 once invoked, about $0.0002 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
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".