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 kaisa-kucherenko/claude-code-flow --skill pytest-qualitygit clone --depth 1 https://github.com/kaisa-kucherenko/claude-code-flowWrote 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/kaisa-kucherenko/claude-code-flow/pytest-quality)<a href="https://agentmods.dev/skills/kaisa-kucherenko/claude-code-flow/pytest-quality"><img src="https://agentmods.dev/badge/skills/kaisa-kucherenko/claude-code-flow/pytest-quality/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/kaisa-kucherenko/claude-code-flow/pytest-quality"><img src="https://agentmods.dev/badge/skills/kaisa-kucherenko/claude-code-flow/pytest-quality.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.00082 | $0.02932 |
| Opus 5.5 | $0.00033 | $0.01173 |
| Sonnet 5.5 | $0.00016 | $0.00586 |
| Haiku 4.5 | $0.00008 | $0.00293 |
Grade C, and why
pytest-quality scanned grade C with 1 finding 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 11d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
find "${TMPDIR:-/tmp}" -maxdepth 1 -name 'pytest-mutation.*' -mmin +120 -exec rm -rf {} + How it starts
The opening of the file, as written. The whole thing — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.
pytest quality bar
A test earns its place by failing on a plausible bug. Count and line coverage are not goals: a suite of ten tests that each catch a distinct break beats fifty that pass whatever the code does, and every extra test is maintenance forever.
0. Project context comes first
Before anything else, read .claude/testing.md in the project root if it exists — run
command, asyncio mode, mock edge, conventions, gitignored files the tests need, traps. If it
does not exist, derive the same from pyproject.toml ([tool.pytest.ini_options]), the
conftest.py nearest the target, and two or three adjacent test files, and say in the
report that the project file is missing.
Project conventions override style preferences here; they never override sections 1–5.
Existing tests are not automatically the standard. A pattern this skill rejects (bare
assert_called(), is not None as the only check) stays rejected even if half the suite
does it.
1. The gate — before writing a test body
- Name the break. State the production change that makes this test fail: wrong branch, wrong constant or argument, missing side effect, skipped validation, wrong boundary, empty/default return. Cannot name one → do not write the test.
- Bug or decision? If only intentional decisions fail it (a constant's value, exact message wording, private structure), it is a change detector: it fires on redesign and sleeps through bugs. Test the behavior that depends on the decision instead.
- Independent expected value. Literals and hand-checked fixtures. Never computed with the code under test, its helpers, or its constants — an oracle that shares the logic shares the bug. Never pasted from a run of the current code: that confirms the code matches itself. Characterization (pinning current behavior of legacy code) is allowed only when asked for, labeled as such in the test name or docstring, and each pinned value cross-checked against the raw input.
- Discriminating values. Distinct, non-default inputs so a dropped, defaulted or swapped
argument fails. When a value can come from several sources (default / config / explicit
argument), give each a different value, or picking the wrong source still passes.
0,"",None, empty and equal values are still covered when they are boundaries.
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.
- 11d ago First seen · 209 lines · 82 tokens per session scan C 9f7b1a433f0b
pytest-quality is a skill published in the GitHub repository kaisa-kucherenko/claude-code-flow (23 stars, last pushed 4d ago), licensed MIT. It adds 82 tokens to every session and 2,932 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-08.
Other skills, from other repositories
test-master
Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…
migrate-xunit-to-xunit-v3
Migrate .NET test projects from xUnit.net v2 to xunit.v3 and fix v3 breaks. Use for package/CPM conversion, OutputType=Exe, preserving the VSTest or MTP runner (including projects currently using YTest.MTP.XUnit2), incompatible TFMs, async void tests, string-to-Type attributes, custom Fact/Theory/BeforeAfterTest…
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
dart-test
DART Test: unit tests, integration tests, CI validation, and debugging.
principle-test-behavior-not-implementation
Apply when you write, change, or keep a test. Assert what the code's users can observe, so that the test fails when that behavior breaks and keeps passing when only the internals change.
restore-internals-seams-in-finally-blocks-after-each-test
When delegating a task affected by this skill, include.