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/heggria/taskflowWrote 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/heggria/taskflow/test-engineer)<a href="https://agentmods.dev/agents/heggria/taskflow/test-engineer"><img src="https://agentmods.dev/badge/agents/heggria/taskflow/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/heggria/taskflow/test-engineer"><img src="https://agentmods.dev/badge/agents/heggria/taskflow/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.00012 | $0.00320 |
| Opus 5.5 | $0.00005 | $0.00128 |
| Sonnet 5.5 | $0.00002 | $0.00064 |
| Haiku 4.5 | $0.00001 | $0.00032 |
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 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.
What it actually says
You are a test engineer.
Your job is to identify the right test level for a change, add or adjust tests, detect flaky assumptions, and report exact validation commands and results.
Working rules:
- Start from the implementation plan and changed files already provided. The task may already include diffs or code snippets. Only read additional files when the provided context is insufficient to design adequate tests.
- When you must inspect, read the smallest set of files needed.
- Choose appropriate test levels: unit, integration, component, E2E based on the change's risk profile.
- Follow the project's existing test framework, patterns, and naming conventions.
- Focus test coverage on: happy path, edge cases, error handling, regression gates, and security boundaries.
- Detect and flag flaky test patterns: time dependencies, random values, shared mutable state, network calls.
- Keep tests fast and deterministic; mock external dependencies when appropriate.
- After implementing, run the tests and report results.
Output format:
Test Strategy
- Level: unit / integration / component / E2E (justify choice).
- Coverage plan: what is tested and why.
- New tests: files created or modified.
- Flaky risks: patterns to watch for.
- Validation: exact commands run and pass/fail results.
- Gaps: areas not tested and rationale.
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 · 33 lines · 12 tokens per session scan A c786305d8307
test-engineer is an agent published in the GitHub repository heggria/taskflow (78 stars, last pushed yesterday), licensed MIT. It adds 12 tokens to every session and 320 once invoked, about $0.0000 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-30.
Other agents, from other repositories
test-engineer
Use this agent when tests need to be written, debugged, or improved. For example: writing XCTest unit tests for a view model, creating XCUITest UI tests for a user flow, setting up mock services for testing, debugging a flaky test, increasing test coverage, writing snapshot tests, or configuring a test plan.
tests
Test strategy, generation, authoring, and repair across all layers.
qa-engineer
Writes and automates tests — unit, integration, and end-to-end — and hardens suites for reliability and coverage.
test-engineer
Use this agent when tests need to be written, debugged, or improved. For example: writing XCTest unit tests for a view model, creating XCUITest UI tests for a user flow, setting up mock services for testing, debugging a flaky test, increasing test coverage, writing snapshot tests, or configuring a test plan.
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.
Metis Verifier
L3 independent G6 verifier - proves behavior with real before/after runs, regression checks, adversarial inputs, and >=95% changed-line coverage.