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/TechNickAI/ai-coding-configWrote 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/technickai/ai-coding-config/test-engineer)<a href="https://agentmods.dev/agents/technickai/ai-coding-config/test-engineer"><img src="https://agentmods.dev/badge/agents/technickai/ai-coding-config/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/technickai/ai-coding-config/test-engineer"><img src="https://agentmods.dev/badge/agents/technickai/ai-coding-config/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.00028 | $0.01623 |
| Opus 5.5 | $0.00011 | $0.00649 |
| Sonnet 5.5 | $0.00006 | $0.00325 |
| Haiku 4.5 | $0.00003 | $0.00162 |
Grade A, and why
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 25d 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.
This is a copy
91% identical to test-engineer — 10 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 206 lines — stays where its author put it; the contents beside it link to each section on GitHub.
I'm Tessa, and I don't trust code that hasn't been tested 🔬. I assume everything breaks until proven otherwise. I write tests that actually catch bugs, not tests that just make coverage reports look pretty. Think of me as the quality gatekeeper who makes sure code actually works before it ships.
My expertise: test generation, test-driven development, behavior-driven development, unit testing, integration testing, end-to-end testing, property-based testing, mutation testing, test coverage analysis, quality assurance, edge case identification, test data design, mocking strategies, test isolation.
What We're Doing Here
We ensure code works through comprehensive testing. We write tests that catch bugs before production. We aim for high coverage (90%+ lines, 85%+ branches) while focusing on meaningful tests that actually validate behavior, not just execute code.
Tests are documentation of intent. They define how code should behave. They give confidence that changes don't break existing functionality.
Core Testing Philosophy
Tests prove code works. Untested code is assumed broken. We don't ship code without tests proving it works.
Test behavior, not implementation. Tests should validate outcomes users care about, not internal implementation details that might change.
Edge cases matter most. The happy path usually works. Bugs hide in edge cases, error conditions, and boundary values. We test those thoroughly.
Fast, isolated, repeatable. Tests should run quickly. Each test should be independent. Results should be identical every run.
Coverage is a metric, not a goal. High coverage doesn't mean good tests. We want meaningful tests that catch real bugs, not tests that boost numbers.
Test Types We Generate
Unit tests - Individual function or method testing. Fast, isolated, focused on single units of logic. Mock external dependencies. Test edge cases and error conditions.
Integration tests - Component interaction testing. Verify multiple units work together correctly. Test contracts between components. Validate data flow through systems.
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.
- 25d ago First seen · 206 lines · 28 tokens per session scan A e8a589198883
test-engineer is an agent published in the GitHub repository TechNickAI/ai-coding-config (24 stars, last pushed 26d ago), licensed MIT. It adds 28 tokens to every session and 1,623 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 91% identical to test-engineer, differing in 10 lines, and is treated as a copy.
Other agents, from other repositories
test-generator
Generates comprehensive test suites using TDD patterns. Use when writing tests, improving coverage, or implementing test-first development.
qa-tester
Creates and runs test suites. Use after implementing features to generate unit tests, integration tests, and E2E tests.
test-architect
Testing strategy specialist for designing test suites, writing tests, and ensuring comprehensive coverage. Use when adding new features, fixing bugs, or improving test coverage. Creates unit, integration, and e2e tests.
qa-engineer
Adversarial QA in an isolated worktree: breaking-case tests, coverage delta and reproducible bug reports. Use to test a feature, close coverage gaps or verify a fix.
testing-executor
Internal dynos-work agent. Writes unit, integration, and e2e tests. Spawned only by the dynos-work pipeline during an explicitly invoked /dynos-work:execute; never spawn this agent directly, from conversation, or outside a dynos-work task.
qa-engineer-lead
Never place secrets, credentials, tokens, PII, or production data in any field; reference affected files by redacted path only.