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-writergit 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-writer)<a href="https://agentmods.dev/skills/rysh-ai/rysh-cli-code/test-writer"><img src="https://agentmods.dev/badge/skills/rysh-ai/rysh-cli-code/test-writer/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-writer"><img src="https://agentmods.dev/badge/skills/rysh-ai/rysh-cli-code/test-writer.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.00016 | $0.00206 |
| Opus 5.5 | $0.00006 | $0.00082 |
| Sonnet 5.5 | $0.00003 | $0.00041 |
| Haiku 4.5 | $0.00002 | $0.00021 |
Grade A, and why
test-writer 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 write tests for existing code.
The bar
A test earns its place only if it fails without the behaviour it covers. Before you finish, verify that: comment out or revert the behaviour, run the test, confirm it fails, then restore. A test that passes either way is worse than no test — it costs runtime and buys false confidence.
Method
- Read the code under test. Find the branches that are not exercised.
- Prefer one honest test of a real failure mode over five shallow ones.
- Use the project's existing test conventions — read a neighbouring test file first rather than importing a framework the project does not use.
- Run
test_runand make sure the suite is green before you report.
Never
Never weaken an assertion to make a test pass. If the code is wrong, say the code is wrong and stop.
What ships with it
3 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 · 27 lines · 16 tokens per session scan A c9bf43dd93b1
test-writer 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 16 tokens to every session and 206 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
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.
test-driven-development
Writing code with tests first: RED-GREEN-REFACTOR, reproduce bugs as failing tests before fixing, and avoid testing anti-patterns. Use when implementing behaviour, fixing a defect, or asked to add tests.
rpa-gen-rules
Use when the user invokes /rpa-gen-rules or asks to create, refresh, audit, or synchronize project instructions such as root AGENTS.md, Cursor .cursor/rules, or Claude Code .claude/rules, especially when existing rule trees have drifted.
rpa-feat
Run when the user invokes /rpa-feat together with a clear feature description (for example issue text). BDD workflow: plan, failing tests, implementation, green tests, full suite, docs and examples, linter at the end. Will not work correctly without the user supplying what to build.
pixiv-cli-test
Select and run pixiv-cli regression, TDD, document, SDK, CLI/MCP, and build checks. Use when changing behavior, reproducing a bug, choosing test scope, or reporting readiness. Separates offline fixtures, native evidence, and explicitly authorized live API tests.