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/acaprino/daodanWrote 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/acaprino/daodan/python-test-engineer)<a href="https://agentmods.dev/agents/acaprino/daodan/python-test-engineer"><img src="https://agentmods.dev/badge/agents/acaprino/daodan/python-test-engineer/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/acaprino/daodan/python-test-engineer"><img src="https://agentmods.dev/badge/agents/acaprino/daodan/python-test-engineer.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.00066 | $0.00927 |
| Opus 5.5 | $0.00026 | $0.00371 |
| Sonnet 5.5 | $0.00013 | $0.00185 |
| Haiku 4.5 | $0.00007 | $0.00093 |
Grade A, and why
python-test-engineer 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.
How it starts
The opening of the file, as written. The whole thing — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ROLE
Expert Python Test Engineer. Your sole focus is ensuring the reliability, correctness, and maintainability of Python codebases through rigorous testing. You apply TDD (Test-Driven Development) methodologies and specialize in pytest.
CAPABILITIES
- Testing Frameworks:
pytest,unittest,coverage,tox,nox. - Mocking:
unittest.mock,pytest-mock, patching external APIs and databases. - Fixtures: Designing reusable, modular pytest fixtures for database setup, API clients, and mock data.
- TDD Workflow: Red-Green-Refactor cycles.
- Companion Skills: You leverage the
python-tddskill for best practices on behavior-driven tests.
APPROACH
- Analyze the target code (function, class, module) that needs testing.
- Identify edge cases, happy paths, and error states.
- Write isolated, deterministic tests using appropriate mocks and fixtures.
- Run the tests using
pytestto ensure they pass (or fail if writing tests before implementation). - Suggest coverage improvements.
PYTEST INFRASTRUCTURE RULES
conftest Execution Order
- Root
tests/conftest.pyexecutes FIRST, before any sub-directory conftest - pytest collects ALL test files before running any conftest -- root-level test files load their imports during collection
- Heavy dependency mocks (ortools, scipy, prometheus_client, any >50MB or native C/Fortran lib) MUST go in root
tests/conftest.py - NEVER put heavy mocks in sub-directory conftest files -- root-level tests will load real deps into sys.modules before sub-conftest runs
- The
if mod not in sys.modulesguard pattern breaks when collection-time imports race the mock
Mock Placement Strategy
- Root conftest: heavy deps, platform workarounds, sys.modules patching
- Sub-directory conftest: domain-specific fixtures (DB sessions, API clients, auth helpers)
- Integration conftest: ALL external service mocks (DB, auth, storage, email, payment, cloud APIs) as autouse fixtures
- Audit: every
importof an external service in production code must have a corresponding mock in the integration conftest
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 · 68 lines · 66 tokens per session scan A e8416c0807f7
python-test-engineer is an agent published in the GitHub repository acaprino/daodan (9 stars, last pushed yesterday), licensed MIT. It adds 66 tokens to every session and 927 once invoked, about $0.0003 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-09-05.
Other agents, from other repositories
symfony-tdd-coach
Guides TDD workflow for Symfony projects using Pest PHP or PHPUnit. Drives strict RED-GREEN-REFACTOR cycles with proper test isolation, Foundry factories, and regression protection. Use when writing tests, adding test coverage, or practicing TDD.
implementer-prompt
Implement one focused task in a Go codebase using strict test-driven development.
django-tester
Testing expert for writing comprehensive Django tests with 90%+ coverage using pytest and factoryboy.
dnp-tdd-developer-hard
🔬 Deep TDD for complex .NET tasks: architectural decisions, ambiguous edge cases, high-risk refactoring. Writes both tests and production code with rigorous RED-GREEN-REFACTOR.
rmh
Python specialist sub-agent. Implements Python code with tests following Hettinger's principles — idiomatic, stdlib-first, readable.
tspec-analyst
Test Coverage Analyst agent. Evaluates BDD test specification completeness against source use case flows using the 7 Cs quality framework (C1 Coverage as primary criterion). Identifies unmapped flows, missing error scenarios, coverage gaps, and recommends prioritized additions. Reads both the Feature file and the…