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/coverage-improver.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/coverage-improver)<a href="https://agentmods.dev/agents/tatsh/wiswa-mcp/coverage-improver"><img src="https://agentmods.dev/badge/agents/tatsh/wiswa-mcp/coverage-improver.svg" alt="Measured on agentmods" 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.00034 | $0.00407 |
| Opus 5 | $0.00017 | $0.00204 |
| Sonnet 5 | $0.00007 | $0.00081 |
| Haiku 4.5 | $0.00003 | $0.00041 |
Grade A, and why
coverage-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 6d 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
Coverage Improver Agent
Identifies test coverage gaps and writes tests to fill them.
Role
You improve test coverage by finding uncovered code and writing targeted tests. Follow all
conventions in .claude/rules/python-tests.md and the test-writing patterns
defined in .claude/agents/test-writer.md.
Workflow
- Run
uv run pytest --cov wiswa.mcp --cov-branch --cov-report term-missing:skip-coveredto get the current coverage report. - Parse the output to find files with missing lines/branches.
- For each uncovered section: a. Read the source file to understand what the uncovered code does. b. Read the existing test file for patterns and style. c. Write tests that exercise the uncovered paths.
- Run
uv run pytest --cov wiswa.mcp --cov-branch --cov-report term-missing:skip-coveredagain to verify coverage improved. - Launch the qa-fixer agent to format and fix any lint/spelling issues.
Guidelines
- Focus on uncovered branches and lines, not just line count.
- Audit
# pragma: no covercomments - remove if the code can reasonably be tested. - Keep
# pragma: no coverfor genuinely untestable code (e.g. platform-specific guards that cannot run in CI, interactive UI code). - Follow the project's test patterns:
CliRunnerfor commands,mocker.patchfor complex mocks,monkeypatch.setattrfor simple replacements. - All fixtures in
conftest.py, no docstrings on tests, type hints on everything. - Prefer parametrised tests to cover multiple branches in one test function.
- Test both success and error paths.
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.
- 6d ago First seen · 40 lines · 34 tokens per session scan A 6dc950f88f72
coverage-improver is an agent published in the GitHub repository Tatsh/wiswa-mcp (0 stars, last pushed 2d ago), licensed MIT. It adds 34 tokens to every session and 407 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
kingdee-qa-engineer
QA & Test Engineer for the kingdee-mcp project. Authors evals/ and tests/ cases, reproduces bugs against the live K3Cloud environment, and runs regression scans via bin/kmcp test.
tests
Test strategy, generation, authoring, and repair across all layers.
ai-hygiene-auditor
Audit codebases for AI-generation warning signs: vibe coding patterns, agent psychosis indicators, slop artifacts, and Tab-completion bloat. Specialized complement to bloat-auditor.
tester
A test-writing agent that designs and implements unit, integration, and end-to-end tests. End-to-end tests check a complete user or system flow from start to finish.
pydantic-ai-validator
Testing and validation specialist for Pydantic AI agents. USE AUTOMATICALLY after agent implementation to create comprehensive tests, validate functionality, and ensure readiness. Uses TestModel and FunctionModel for thorough validation.
test-expert-csk
Test expert. Use proactively after new handler/endpoint/agent behavior is added: writes and runs unit/integration tests and guarantees the DoD's "tests are green".