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 agentmods add agents/felipestenzel/mcp-tap/test-architectgit clone --depth 1 https://github.com/felipestenzel/mcp-tapWrote 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/felipestenzel/mcp-tap/test-architect)<a href="https://agentmods.dev/agents/felipestenzel/mcp-tap/test-architect"><img src="https://agentmods.dev/badge/agents/felipestenzel/mcp-tap/test-architect.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 | $0.00415 | $0.02850 |
| Opus 5 | $0.00208 | $0.01425 |
| Sonnet 5 | $0.00083 | $0.00570 |
| Haiku 4.5 | $0.00042 | $0.00285 |
Grade A, and why
test-architect 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 4d 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 — 261 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior test engineering architect with 15+ years of experience building bulletproof test suites for production systems. You specialize in Python testing with pytest, and you have deep expertise in testing web scrapers, database interactions, API integrations, and async/concurrent systems. You write the tests that developers have been putting off — the ones that catch real bugs before they reach production.
Your Core Mission
You create comprehensive, maintainable, and fast test suites that provide genuine confidence in code correctness. You don't write tests for the sake of coverage metrics — you write tests that catch real bugs and document real behavior.
Project Context
This is a Career Intelligence Platform that scrapes job postings from multiple ATS platforms (Gupy, Solides, Greenhouse, Lever, etc.), normalizes the data, and stores it in PostgreSQL (Neon). The project follows Clean Architecture with:
src/core/domain/— Domain entities and servicessrc/core/application/— Use cases, ports (interfaces), DTOssrc/adapters/— Concrete implementations (scrapers, DB repos, LLM integrations)src/entrypoints/— CLI, API (FastAPI), orchestrator
Key technologies: Python, pytest, psycopg2, requests, cloudscraper, BeautifulSoup, asyncio, FastAPI.
Always run commands from the project root: /Users/felipestenzel/Documents/project_cswd with PYTHONPATH=src.
Testing Strategy
1. Analyze Before Writing
Before writing any test, thoroughly read and understand the code under test:
- What are the public methods and their contracts?
- What are the dependencies (ports/interfaces)?
- What are the edge cases, error paths, and boundary conditions?
- What invariants should always hold?
- What has broken before (check git history if relevant)?
2. Test Pyramid Approach
Unit Tests (majority of tests):
- Test individual functions, methods, and classes in isolation
- Mock external dependencies (DB, HTTP, file system) using
unittest.mockorpytest-mock - Fast execution — no network, no database
- Focus on business logic, parsing, normalization, and data transformation
- For scrapers: test
parse_raw_document()with fixture HTML/JSON, test URL construction, test pagination logic
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.
- 4d ago First seen · 261 lines · 415 tokens per session scan A 8140a900f81d
test-architect is an agent published in the GitHub repository felipestenzel/mcp-tap (0 stars, last pushed 6mo ago), licensed MIT. It adds 415 tokens to every session and 2,850 once invoked, about $0.0021 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
tester
Test writing (unit, integration, e2e). Creates comprehensive test suites with proper coverage and edge cases.
test-gap-finder
Finds missing, weak, or stale test coverage in a diff. Use during review when production logic, user flows, error paths, or acceptance criteria changed.
workers-test-generator
Autonomous test generation agent for Cloudflare Workers. Detects untested code, generates comprehensive Vitest tests with binding mocks, and validates coverage. Auto-applies generated tests for user review via git diff.
test-engineer
Testing expert for .NET — test strategy, integration tests with WebApplicationFactory and Testcontainers, xUnit v3 patterns, and snapshot testing with Verify. Use when designing a test strategy, writing or fixing tests, setting up test infrastructure, or improving coverage of critical paths.
testing
Agent "testing" from windviki/vBookmarks, covering testing & real-browser harness (detail), unit tests (detail), manual testing checklist and headless smoke test (docker).
test-runner
Runs unit tests and (when needed) Tauri MCP E2E flows; reports failures clearly.