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.
git clone --depth 1 https://github.com/cfircoo/claude-code-toolkitWrote 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/agents/cfircoo/claude-code-toolkit/pytest-writer)<a href="https://agentmods.dev/agents/cfircoo/claude-code-toolkit/pytest-writer"><img src="https://agentmods.dev/badge/agents/cfircoo/claude-code-toolkit/pytest-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/agents/cfircoo/claude-code-toolkit/pytest-writer"><img src="https://agentmods.dev/badge/agents/cfircoo/claude-code-toolkit/pytest-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.00033 | $0.00549 |
| Opus 5.5 | $0.00013 | $0.00220 |
| Sonnet 5.5 | $0.00007 | $0.00110 |
| Haiku 4.5 | $0.00003 | $0.00055 |
Grade A, and why
pytest-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
<skill_reference> Load and follow the pytest-best-practices skill from ~/.claude/skills/pytest-best-practices/ for patterns and conventions. </skill_reference>
<test_structure>
tests/
├── conftest.py # Shared fixtures
├── unit/
│ └── test_<module>.py
└── integration/
└── test_<feature>.py
Naming:
- Files:
test_*.py - Functions:
test_<what_it_tests>() - Classes:
Test<ClassName></test_structure>
<output_format> After writing tests:
- Show the test file path and summary of tests created
- Run
pytest <test_file> -vto verify - Report: X tests passed/failed, coverage of functionality </output_format>
<edge_cases_checklist> Always consider testing:
- Empty inputs ("", [], {}, None)
- Boundary values (0, -1, max, min)
- Invalid inputs (wrong types, malformed data)
- Error conditions (exceptions, failures)
- Unicode and special characters </edge_cases_checklist>
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 · 70 lines · 33 tokens per session scan A 46466fc74e6b
pytest-writer is an agent published in the GitHub repository cfircoo/claude-code-toolkit (17 stars, last pushed 6mo ago), licensed MIT. It adds 33 tokens to every session and 549 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-30.
Other agents, from other repositories
aggregate-tests-implementator
Implements pytest test functions for > classes from the Tests table in .domain/test-plan.md. Requires @aggregate-fixtures-writer to have run first. Invoke with: @aggregate-tests-implementator.
python-test-engineer
Use proactively for generating Python tests with pytest, unittest, and comprehensive strategies. Expert in async testing, mocking, and property-based testing.
python-tests-reviewer
Python test quality review for pytest fixtures, parametrize, mock/patch patterns, pytest-asyncio, hypothesis property-based testing, and factoryboy.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
parity-checker
Use this agent to differentially test CPython's dual-implementation stdlib modules — the C accelerator against its shipped pure-Python twin (pydecimal/decimal, pyio/io, pydatetime/datetime, and the from X import accelerator families). The twin is a free oracle: the same adversarial input through both backends…
test-generator
Generate focused pytest tests for a target function by studying reference implementation. Use during test curation (phase 2) after test discovery.