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 fady-ramzy91/community-ai-skills --skill clean-unit-testinggit clone --depth 1 https://github.com/fady-ramzy91/community-ai-skillsWrote 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/fady-ramzy91/community-ai-skills/clean-unit-testing)<a href="https://agentmods.dev/skills/fady-ramzy91/community-ai-skills/clean-unit-testing"><img src="https://agentmods.dev/badge/skills/fady-ramzy91/community-ai-skills/clean-unit-testing/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/fady-ramzy91/community-ai-skills/clean-unit-testing"><img src="https://agentmods.dev/badge/skills/fady-ramzy91/community-ai-skills/clean-unit-testing.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.00088 | $0.01150 |
| Opus 5 | $0.00044 | $0.00575 |
| Sonnet 5 | $0.00018 | $0.00230 |
| Haiku 4.5 | $0.00009 | $0.00115 |
Grade A, and why
clean-unit-testing 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 10d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clean Unit Testing (Clean Code, Ch. 9)
Apply these rules every time you write, generate, refactor, or review unit tests. Language and framework may vary; the principles do not.
Non-negotiable principles
1. Three Laws of TDD (order is mandatory)
- Do not write production code until a failing unit test exists.
- Do not write more of a unit test than is sufficient to fail (compile failure counts as failure).
- Do not write more production code than is sufficient to pass the currently failing test.
Workflow: red → green → refactor. Prefer the smallest possible step.
If the user asks to "implement then test", push back once and propose test-first. If they insist, still write behavior-focused, single-concept tests afterward — never rubber-stamp buggy code.
2. Tests are first-class code
- Test code is as important as production code — not a second-class citizen.
- Prefer deleting or rewriting dirty tests over letting them rot.
- Never leave
print/console.log/ log-only checks as the verification step.
3. One concept per test
- Each test function verifies one behavior / one concept.
- Multiple asserts are OK only if they verify the same concept.
- Split kitchen-sink tests (
test1, “comprehensive”, “checks everything”) into separate named tests.
4. F.I.R.S.T.
| Rule | Requirement |
|---|---|
| Fast | No real network, disk DB, or heavy I/O. Use fakes/stubs/in-memory doubles. |
| Independent | No shared mutable state; no order dependence; reset in setup/teardown if needed. |
| Repeatable | Inject clock/time, randomness, locale, and environment — never rely on wall clock or live services. |
| Self-validating | Assert true/false (or equivalent). Never require a human to read output. |
| Timely | Write the test with (preferably before) the production code it covers. |
5. Readability first
- Names must describe behavior:
subject_condition_expectedor`given X when Y then Z`. - A failing test name at 2 a.m. should explain what broke without opening the body.
- Prefer Given-When-Then structure in the body when it aids clarity.
- Prefer asserting outcomes over verifying every mock interaction.
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.
- 10d ago First seen · 113 lines · 88 tokens per session scan A 9ff2555b706f
clean-unit-testing is a skill published in the GitHub repository fady-ramzy91/community-ai-skills (1 stars, last pushed 16d ago), licensed MIT. It adds 88 tokens to every session and 1,150 once invoked, about $0.0004 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
cpp-testing
Use only when writing/updating/fixing C++ tests, configuring GoogleTest/CTest, diagnosing failing or flaky tests, or adding coverage/sanitizers.
rust-testing
Rust testing patterns including unit tests, integration tests, async testing, property-based testing, mocking, and coverage. Follows TDD methodology.
write-vibe-tests
Write or refactor Mistral Vibe tests with proper decoupling. Use when adding behavior coverage, testing ports/adapters, replacing brittle mocks, creating fakes, adding characterization tests before refactors, or changing tests under tests/ for vibe/core, vibe/cli, vibe/acp, tools, config, sessions, skills, hooks, MCP…
composing-matchers
Build compound Gomega assertions by combining matchers — And/SatisfyAll (all pass), Or/SatisfyAny (any pass), Not (negate), WithTransform to map the actual before matching, Satisfy for an ad-hoc predicate, HaveValue to dereference pointers/interfaces, HaveField for struct fields and method results, HaveEach for every…
nw-fp-clojure
Clojure language-specific patterns, data-first modeling, REPL-driven development, and spec.
nw-fp-fsharp
F# language-specific patterns, Railway-Oriented Programming, and Computation Expressions.