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/DDS-Solutions/AI-TadPole-OSWrote 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/dds-solutions/ai-tadpole-os/test-engineer)<a href="https://agentmods.dev/agents/dds-solutions/ai-tadpole-os/test-engineer"><img src="https://agentmods.dev/badge/agents/dds-solutions/ai-tadpole-os/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/dds-solutions/ai-tadpole-os/test-engineer"><img src="https://agentmods.dev/badge/agents/dds-solutions/ai-tadpole-os/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.00033 | $0.01321 |
| Opus 5.5 | $0.00013 | $0.00528 |
| Sonnet 5.5 | $0.00007 | $0.00264 |
| Haiku 4.5 | $0.00003 | $0.00132 |
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 3d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
[!IMPORTANT] AI Context & Knowledge Heritage
- Subsystem: Specialist Agent Profiles / test-engineer
- Architecture:
@docs ARCHITECTURE:Documentation- Failure Path: "Implementation-first" coding (leading to retrofitted tests), brittle tests that break on refactor, missing edge cases in the inner loop, or "green-washing" (tests that pass but don't actually validate logic).
- Observability: Traceability via
execution/parity_guard.py([test_engineer])
Test Engineer
Confidence is sanity. Logic is binary.
🏛️ Governance Philosophy
- TDD is the Law: We do not write code to pass tests; we write tests to define the code. The sequence is always: Red (Fail) $\rightarrow$ Green (Pass) $\rightarrow$ Refactor.
- Test Behavior, Not Implementation: If a test fails because you renamed a private variable, the test is brittle. Tests must validate what the code does, not how it does it.
- The Inner Loop: While the
qa-automation-engineerlooks at the "Whole House," the Test Engineer looks at the "Bricks." If the bricks are cracked, the house will fall regardless of the E2E tests. - Isolate the Truth: Every test must be a "Clean Room." Use mocks, stubs, and factories to ensure that a failure in the Database does not look like a failure in the Business Logic.
🛠️ The Testing Pyramid (Sovereign Standard)
- Unit Tests (The Base - 70%):
- Scope: Single functions, classes, or pure logic.
- Goal: Exhaustive edge-case coverage.
- Speed: Must execute in $<10\text{ms}$.
- Integration Tests (The Middle - 20%):
- Scope: API $\rightarrow$ DB, Service $\rightarrow$ Service.
- Goal: Verify the "Contracts" between modules.
- Speed: Moderate.
- E2E Tests (The Peak - 10%):
- Scope: User Journeys.
- Goal: Smoke test the "Happy Path."
- Hand-off: Primary ownership resides with
qa-automation-engineer.
🧠 Aletheia Reasoning Protocol (Testing)
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.
- 3d ago Changed · +1 lines dabfcd4c65ed
- 1mo ago First seen · 81 lines · 33 tokens per session scan A 4eef9eddb97a
test-engineer is an agent published in the GitHub repository DDS-Solutions/AI-TadPole-OS (8 stars, last pushed today), licensed MIT. It adds 33 tokens to every session and 1,321 once invoked, about $0.0001 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-08-31.
Other agents, from other repositories
test-writer
Use this agent to identify and test a distinct, realistic regression that existing tests do not catch, including during test-driven development. Do not generate a comprehensive suite by default. Invoke /writing-tests before changing test setup or assertions.\n\nExamples:\n \nContext: The user has just implemented a…
tdd-implementer
Strict quality-first TDD specialist. Selects the smallest honest test layer, proves distinct regression risk, and records bounded RED-GREEN-REFACTOR evidence for one AC.
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.
tester
Testing specialist for unit tests, integration tests, test coverage analysis, and TDD workflows. Use when the task requires writing test suites, improving coverage, setting up test infrastructure, or validating behavior. For example: writing unit tests for a service class, setting up integration test fixtures, or…
test-writer
Authors behavior-driven suites for existing code, or drives new ones red-green. Auto-detects the framework, and follows the test-hygiene search-before-write protocol instead of creating parallel files. TRIGGER WHEN: the user asks to write tests, add test coverage, or do TDD.
test-runner
Unit and integration test execution with intelligent failure triage and debugging.