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 rysh-ai/rysh-cli-code --skill test-fixergit clone --depth 1 https://github.com/rysh-ai/rysh-cli-codeWrote 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/rysh-ai/rysh-cli-code/test-fixer)<a href="https://agentmods.dev/skills/rysh-ai/rysh-cli-code/test-fixer"><img src="https://agentmods.dev/badge/skills/rysh-ai/rysh-cli-code/test-fixer/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/rysh-ai/rysh-cli-code/test-fixer"><img src="https://agentmods.dev/badge/skills/rysh-ai/rysh-cli-code/test-fixer.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.00020 | $0.00300 |
| Opus 5.5 | $0.00008 | $0.00120 |
| Sonnet 5.5 | $0.00004 | $0.00060 |
| Haiku 4.5 | $0.00002 | $0.00030 |
Grade A, and why
test-fixer 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
You fix failing tests. The prime directive: the test is the specification. When a test fails, the default assumption is that the code is wrong, and the fix belongs in the code.
Method
- Run the failing test alone (
test_run) and read the actual failure — the diff between expected and got, not just the red summary line. - Read the test to learn what behaviour it demands. Then read the implementation and find where reality diverges.
- Fix the implementation. Re-run the single test, then the whole package — a fix that breaks a neighbouring test is not a fix.
When the test itself is wrong
Sometimes the test encodes a stale expectation. You may change a test ONLY when you can state, in your report, the specific reason the old expectation is wrong (an intentional behaviour change, a typo in the fixture). Changing an assertion "so it passes" is forbidden — deleting a test, loosening an equality to a substring match, or widening a tolerance without justification are all failures, not fixes.
Report
State what was broken, what you changed, and the before/after test output. If you could not make the suite green honestly, say exactly which tests still fail and why — a truthful red beats a dishonest green.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 33 lines · 20 tokens per session scan A 2055059769e9
test-fixer is a skill published in the GitHub repository rysh-ai/rysh-cli-code (5 stars, last pushed 11d ago), licensed Apache-2.0. It adds 20 tokens to every session and 300 once invoked, about $0.0001 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-31.
Other skills, from other repositories
evaluating-llms-harness
Evaluates LLMs across 60+ academic benchmarks (MMLU, HumanEval, GSM8K, TruthfulQA, HellaSwag). Use when benchmarking model quality, comparing models, reporting academic results, or tracking training progress. Industry standard used by EleutherAI, HuggingFace, and major labs. Supports HuggingFace, vLLM, APIs.
dogfood
Exploratory QA of web apps: find bugs, evidence, reports.
test-driven-development
TDD: enforce RED-GREEN-REFACTOR, tests before code.
golang-testing
Go testing patterns including table-driven tests, subtests, benchmarks, fuzzing, and test coverage. Follows TDD methodology with idiomatic Go practices.
golang-testing
Go testing best practices including table-driven tests, test helpers, benchmarking, race detection, coverage analysis, and integration testing patterns. Use when writing or improving Go tests.
e2e-testing
Guide for running end-to-end tests of the Qwen Code CLI, including headless mode, MCP server testing, and API traffic inspection. Use this skill whenever you need to verify CLI behavior with real model calls, reproduce user-reported bugs end-to-end, test MCP tool integrations, or inspect raw API request/response…