Borrowing it
Nothing to install: this file belongs to nuwax-ai/nuwax. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/nuwax-ai/nuwax/main/.claude/commands/test-fix.mdgit clone --depth 1 https://github.com/nuwax-ai/nuwaxWrote 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/nuwax-ai/nuwax/test-fix)<a href="https://agentmods.dev/commands/nuwax-ai/nuwax/test-fix"><img src="https://agentmods.dev/badge/commands/nuwax-ai/nuwax/test-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/nuwax-ai/nuwax/test-fix"><img src="https://agentmods.dev/badge/commands/nuwax-ai/nuwax/test-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.00011 | $0.00208 |
| Opus 5.5 | $0.00004 | $0.00083 |
| Sonnet 5.5 | $0.00002 | $0.00042 |
| Haiku 4.5 | $0.00001 | $0.00021 |
Grade A, and why
test-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 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.
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.
What it actually says
Test & Fix Cycle
-
Run the tests using the project's test runner:
pnpm test -
Analyze failures — For each failing test, extract:
- File path and line number
- Expected vs actual values
- Error message and stack trace
-
Apply fixes — For each failure:
- Read the test file and the source file it tests
- Determine if the fix should be in the test (test was wrong) or the source (bug in code)
- Apply the minimal fix
- Re-run that specific test to verify
-
Re-run full suite — After all fixes, run the full test suite again to catch regressions.
Report a summary: total tests, passed, failed, fixed, and any remaining issues.
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 · 27 lines · 11 tokens per session scan A 1f9352cd460b
test-fix is a command published in the GitHub repository nuwax-ai/nuwax (897 stars, last pushed yesterday), licensed Apache-2.0. It adds 11 tokens to every session and 208 once invoked, about $0.0000 per session on Opus 5.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-09-15.
Other commands, from other repositories
hatch3r-bug-plan
Diagnose a complex incident -- reproduce the symptom, rank root-cause hypotheses, design the fix path, and emit regression coverage items as a board-ready investigation.
hatch3r-bug-pipeline
Run a known-cause bug fix through a 3-phase test-first pipeline -- reproduce + root-cause, regression-test + fix together, then root-cause-depth review -- with full sub-agent delegation.
triage-failed-scenarios
Run the Playwright specs and triage each failing scenario — delete, update and re-record, or report as a defect.
case-design
A controlled workflow that turns requirements documents or prototypes into test cases in Markdown or Excel. TDD means writing tests before implementation; this tool focuses on designing those tests from requirements.
create-repro
Isolate a bug report into a minimal, standalone reproduction script or test case.
debug
Use when a bug needs systematic diagnosis before a fix is attempted.