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/billbuchanan-code/claude-code-power-setup/test-and-fixnpx skills add billbuchanan-code/claude-code-power-setup --skill test-and-fixgit clone --depth 1 https://github.com/billbuchanan-code/claude-code-power-setupWrote 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/skills/billbuchanan-code/claude-code-power-setup/test-and-fix)<a href="https://agentmods.dev/skills/billbuchanan-code/claude-code-power-setup/test-and-fix"><img src="https://agentmods.dev/badge/skills/billbuchanan-code/claude-code-power-setup/test-and-fix.svg" alt="Measured on agentmods" 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 | $0.00019 | $0.00452 |
| Opus 5 | $0.00010 | $0.00226 |
| Sonnet 5 | $0.00004 | $0.00090 |
| Haiku 4.5 | $0.00002 | $0.00045 |
Grade A, and why
test-and-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 4d 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 and Fix Skill
Run the test-fix-verify loop: execute tests, analyze failures, fix issues, and re-run until all tests pass.
Process
-
Discover the test command by checking for:
package.json(look fortest,test:unit,test:integrationscripts)Makefile(look fortesttarget)pytest.ini,pyproject.toml,setup.cfg(Python projects)Cargo.toml(Rust projects — usecargo test)go.mod(Go projects — usego test ./...)- Fall back to common conventions if none found
-
Run tests via Bash. If $ARGUMENTS specifies a test file or pattern, use that instead of the full suite.
-
If tests pass, report success and exit with a summary of what was run.
-
If tests fail, analyze the failure output:
- Identify which tests failed and why
- Extract error messages, stack traces, and assertion details
- Determine the root cause (code bug vs. test bug vs. environment issue)
-
Read the failing test and the code under test to understand the expected behavior.
-
Fix the issue:
- Prefer fixing the application code, not the test, unless the test itself is clearly wrong
- Make minimal, targeted changes
- Explain what was changed and why
-
Re-run tests to verify the fix.
-
Repeat steps 3-7 up to 5 iterations maximum. If tests still fail after 5 attempts, stop and report the remaining issues.
-
Report final results:
- Total iterations performed
- Tests fixed vs. tests still failing
- Summary of all changes made
- Any remaining issues that need manual attention
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.
- 4d ago First seen · 47 lines · 19 tokens per session scan A a2965c1a3cd8
test-and-fix is a skill published in the GitHub repository billbuchanan-code/claude-code-power-setup (2 stars, last pushed 1mo ago), licensed MIT. It adds 19 tokens to every session and 452 once invoked, about $0.0001 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…