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/hgahlot/claude-flowWrote 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/commands/hgahlot/claude-flow/build-fix)<a href="https://agentmods.dev/commands/hgahlot/claude-flow/build-fix"><img src="https://agentmods.dev/badge/commands/hgahlot/claude-flow/build-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/commands/hgahlot/claude-flow/build-fix"><img src="https://agentmods.dev/badge/commands/hgahlot/claude-flow/build-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.00000 | $0.00557 |
| Opus 5 | $0.00000 | $0.00279 |
| Sonnet 5 | $0.00000 | $0.00111 |
| Haiku 4.5 | $0.00000 | $0.00056 |
Grade A, and why
build-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 9d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/build-fix — Systematic Root Cause Debugging
Apply systematic root cause analysis to fix build failures, test failures, and runtime errors.
Instructions
Step 1: Reproduce
- Run the failing command exactly as-is
- Capture the full error output (not just the last line)
- Confirm the failure is reproducible
Step 2: Isolate
- Identify the error type: compile error | test failure | runtime error | config error
- Find the first error in the stack (not the cascading consequences)
- Identify the exact file and line number where the failure originates
Step 3: Hypothesize
Generate 2–3 specific hypotheses for the root cause:
- What changed recently? (
git diff HEAD~1orgit log --oneline -5) - What does the error message literally say?
- What are the dependencies of the failing component?
Step 4: Test Hypothesis (Smallest Change)
- Pick the most likely hypothesis
- Make the SMALLEST possible change to test it
- Re-run — did it change the error? (Better, worse, or same)
- If no improvement, revert and try next hypothesis
Step 5: Fix
- Apply the confirmed fix
- Run the full test suite (not just the failing test)
- Confirm no regressions introduced
Output Format
## Reproduce
Command: <exact command>
Output: <full error — first occurrence>
Status: ✓ Reproducible
## Isolate
Error type: <compile|test|runtime|config>
Root file: <file>:<line>
First error: <exact error message>
## Hypotheses
1. <hypothesis> — likelihood: high/medium/low
2. <hypothesis> — likelihood: high/medium/low
3. <hypothesis> — likelihood: high/medium/low
## Testing Hypothesis 1
Change: <minimal change made>
Result: <new error or resolution>
## Fix Applied
<description of fix>
Full test run: <pass/fail count>
Regressions: none / <list>
## Root Cause
<one sentence explaining what caused the failure and why the fix resolves it>
Rules
- NEVER guess-and-check with multiple changes at once — isolate one variable at a time
- NEVER skip the full test suite after fixing — look for regressions
- If 3 hypotheses fail, escalate: read the dependency source, check changelogs, search error message
- "I don't know" is a valid intermediate state — document what you've ruled out
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.
- 9d ago First seen · 70 lines · 0 tokens per session scan A e4856f1da34d
build-fix is a command published in the GitHub repository hgahlot/claude-flow (53 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 557 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-30.
Other commands, from other repositories
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
fix
Universal debugging and fix application with semantic code analysis.
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
gh-issue-use-cypress
Like /gh-issue-use-browser, but pinned to the Cypress MCP — use when your project runs the Cypress MCP for browser automation. Example — /gh-issue-use-cypress "Composer > Save" saving toasts failure but the record persists.