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 skills add TypedDevs/bashunit --skill fix-testgit clone --depth 1 https://github.com/TypedDevs/bashunitWrote 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/typeddevs/bashunit/fix-test)<a href="https://agentmods.dev/skills/typeddevs/bashunit/fix-test"><img src="https://agentmods.dev/badge/skills/typeddevs/bashunit/fix-test/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/skills/typeddevs/bashunit/fix-test"><img src="https://agentmods.dev/badge/skills/typeddevs/bashunit/fix-test.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00009 | $0.00314 |
| Opus 5.5 | $0.00004 | $0.00126 |
| Sonnet 5.5 | $0.00002 | $0.00063 |
| Haiku 4.5 | $0.00001 | $0.00031 |
Grade A, and why
fix-test 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 5d 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
Fix a failing test
Repository paths are relative to the repository root. Start with reported output and the failing file; use ./bashunit --filter "test_name" <test-file> to reproduce narrowly. Discover with the full suite only when no narrower failure is known.
- Trace the failure to its source and classify it: incorrect expectation/setup, implementation defect, environment/fixture issue, parallel race, or flaky external dependency. Check fixtures under
tests/fixtures/and mocks withassert_have_been_called <name>where relevant. Temporary diagnostics go to stderr and must be removed. - Preserve a failing regression for the actual defect. Correct an expectation only when the intended behavior proves it wrong; otherwise make the smallest implementation fix with TDD. Repair fixtures or setup for environment defects, use the existing
$temp_dirisolation and wait for asynchronous work for races, and mock external dependencies for flaky tests. - Run the focused test until it passes for the right reason. Reproduce relevant parallel behavior when investigating isolation. If the failure may predate the change, verify the same focused test on unchanged main in an isolated checkout.
- Add a relevant edge case if it protects the root cause. After the complete change set, the coordinator runs the canonical quality gate once; delegates run only assigned targeted checks.
Report the cause, fix, focused evidence, and any specific remaining environment limit.
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.
- 5d ago Changed · -38 lines 1f290b51ae52
- 1mo ago First seen · 55 lines · 9 tokens per session scan A ce854a77961d
fix-test is a skill published in the GitHub repository TypedDevs/bashunit (435 stars, last pushed today), licensed MIT. It adds 9 tokens to every session and 314 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-08-30.
Other skills, from other repositories
wispr-flow-debug
Debug and test the Wispr Flow AutoHotkey dictation triggers (Copilot key + extra keys) from WSL by deploying macos.ahk to the Windows Desktop, reloading AutoHotkey, and reading the debug log. Use when an activation/trigger key isn't starting/stopping dictation, when the overlay clicks land wrong, or when verifying a…
writing-nemesis
Guides writing new nemesis (chaos engineering disruptions) for the SCT framework. Use when creating a new NemesisBaseClass subclass, adding disruption logic, setting nemesis flags, or configuring target node pools. Covers the sdcm/nemesis/ package structure, auto-discovery, flag filtering, CI configuration, and unit…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
r-verify-claim
Verify a falsifiable claim about the current state of the codebase.
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.
langsmith-observability
LLM observability platform for tracing, evaluation, and monitoring. Use when debugging LLM applications, evaluating model outputs against datasets, monitoring production systems, or building systematic testing pipelines for AI applications.