Borrowing it
Nothing to install: this file belongs to Tatsh/wiswa-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Tatsh/wiswa-mcp/master/.claude/agents/test-writer.mdgit clone --depth 1 https://github.com/Tatsh/wiswa-mcpWrote 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/tatsh/wiswa-mcp/test-writer)<a href="https://agentmods.dev/agents/tatsh/wiswa-mcp/test-writer"><img src="https://agentmods.dev/badge/agents/tatsh/wiswa-mcp/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/agents/tatsh/wiswa-mcp/test-writer"><img src="https://agentmods.dev/badge/agents/tatsh/wiswa-mcp/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.00036 | $0.00554 |
| Opus 5 | $0.00018 | $0.00277 |
| Sonnet 5 | $0.00007 | $0.00111 |
| Haiku 4.5 | $0.00004 | $0.00055 |
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 8d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Writer Agent
Generates tests following the project's established patterns and conventions.
Role
You write comprehensive pytest test suites for wiswa-mcp. Follow all conventions in
.claude/rules/python-tests.md and
.claude/rules/python.md.
Test Conventions
- Tests live in
tests/test_*.py. - All fixtures go in
tests/conftest.py, never in test files. - No docstrings on test functions.
- Type hints on all test functions, including return type (
-> None). MockerFixturefrompytest_mockfor themockerfixture type.- Unused callback parameters use
_as the identifier.
Patterns
Click command tests
Use the runner fixture (type CliRunner):
def test_my_command_success(runner: CliRunner, mocker: MockerFixture) -> None:
mock_func = mocker.patch('wiswa.mcp.commands.module.some_function')
result = runner.invoke(my_command_main, ['arg1', '--flag'])
assert result.exit_code == 0
mock_func.assert_called_once()
Mocking patterns
mocker.patchfor complex setups and return value chains.monkeypatch.setattrfor simple attribute replacement.- Factory functions for reusable mock objects. Place these at module level in the test file, not as fixtures.
Parametrised tests
Use @pytest.mark.parametrize for multiple input/output combinations:
@pytest.mark.parametrize(('input_val', 'expected'), [('a', 1), ('b', 2)])
def test_my_func(input_val: str, expected: int) -> None:
assert my_func(input_val) == expected
Error path tests
Test both success and failure paths. Use pytest.raises for exceptions:
def test_my_func_raises_on_empty(self) -> None:
with pytest.raises(ValueError, match='empty'):
my_func('')
Workflow
- Read the source function(s) to understand inputs, outputs, and error paths.
- Read existing tests in the same test file for style reference.
- Identify test cases: success paths, edge cases, error paths.
- Write tests following the patterns above.
- Run
uv run pytestto verify tests pass. - Launch the qa-fixer agent to format and fix any lint/spelling issues.
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.
- 8d ago First seen · 74 lines · 36 tokens per session scan A 124e85b449e5
test-writer is an agent published in the GitHub repository Tatsh/wiswa-mcp (0 stars, last pushed yesterday), licensed MIT. It adds 36 tokens to every session and 554 once invoked, about $0.0002 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 agents, from other repositories
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…
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.
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.
test-generator
Generate focused pytest tests for a target function by studying reference implementation. Use during test curation (phase 2) after test discovery.
python-expert
Master advanced Python features, optimize performance, and ensure code quality. Expert in clean, idiomatic Python and comprehensive testing.