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 Notysoty/openagentskills --skill unit-test-improvergit clone --depth 1 https://github.com/Notysoty/openagentskillsWrote 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/notysoty/openagentskills/unit-test-improver)<a href="https://agentmods.dev/skills/notysoty/openagentskills/unit-test-improver"><img src="https://agentmods.dev/badge/skills/notysoty/openagentskills/unit-test-improver/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/notysoty/openagentskills/unit-test-improver"><img src="https://agentmods.dev/badge/skills/notysoty/openagentskills/unit-test-improver.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.00029 | $0.01885 |
| Opus 5.5 | $0.00012 | $0.00754 |
| Sonnet 5.5 | $0.00006 | $0.00377 |
| Haiku 4.5 | $0.00003 | $0.00188 |
Grade A, and why
Unit Test Improver 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.
How it starts
The opening of the file, as written. The whole thing — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Unit Test Improver
What this skill does
This skill directs the agent to review an existing set of unit tests and improve them. It looks for weak or incomplete tests — tests that pass even when the code is broken, tests that don't assert the right things, tests that are missing critical edge cases, and tests that test implementation details instead of behavior. The output is an improved, rewritten test suite that is harder to fool and more useful as a safety net.
Use this before a major refactor (so you can trust the tests will catch regressions), during a code review, or when a bug slips past your existing tests.
How to use
Claude Code / Cline
Copy this file to .agents/skills/unit-test-improver/SKILL.md in your project root.
Then ask:
- "Use the Unit Test Improver skill on
tests/cart.test.ts." - "Review and improve the unit tests for
calculateDiscountusing the Unit Test Improver skill."
Provide both the test file and the code being tested.
Cursor
Add the instructions below to your .cursorrules or paste them into the Cursor AI pane. Then share the test file and the source file side by side.
Codex
Paste both the test file (labeled "TESTS") and the source file (labeled "SOURCE") and ask Codex to follow the instructions below.
The Prompt / Instructions for the Agent
When asked to improve unit tests, follow these steps:
Step 1 — Read both the tests and the source
Read the full test file. Then read the source code being tested. Understand what the function is supposed to do before evaluating whether the tests cover it.
Step 2 — Identify test quality issues
Check every test for these problems:
Weak assertions
expect(result).toBeTruthy()instead ofexpect(result).toBe(true)— passes for any truthy valueexpect(result).toBeDefined()when the actual value should be checkedexpect(fn).not.toThrow()without checking the return value- Asserting on the wrong field (e.g., checking
result.idbut notresult.value)
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 · 214 lines · 29 tokens per session scan A 905eb08486dc
Unit Test Improver is a skill published in the GitHub repository Notysoty/openagentskills (9 stars, last pushed 2mo ago), licensed MIT. It adds 29 tokens to every session and 1,885 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
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
review-ugc-render
Mandatory pre-publish review gate for a UGC video render. Transcribes the finished render's AUDIO with Whisper and word-diffs it against the approved spoken script, then gates pinning the final render (videoprojectupsert patch.finalrenderid) — blocking a render whose generated audio mis-voices a word (e.g. the…
remove-ai-slops
Removes AI-generated code smells from branch changes or an explicit file list behind regression tests. Use when the user asks to clean up, deslop, or remove AI-slop patterns from recent changes.
brooks-test
Test quality review drawing on twelve classic engineering books — with primary focus on xUnit Test Patterns, The Art of Unit Testing, How Google Tests Software, and Working Effectively with Legacy Code — that diagnoses structural problems in an existing test suite: brittleness, mock abuse, coverage illusions, slow…
JavaScript Testing Patterns
Modern JavaScript testing strategies with Jest, Mocha, and testing best practices covering unit testing, integration testing, mocking, async patterns, and DOM testing.
Code Coverage Analysis
Measure and enforce test coverage with Istanbul/nyc, c8, Jest, and Vitest. Covers branch versus line coverage, per-directory thresholds, CI gates, and correctly excluding generated code from reports.