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/heggria/taskflow/test-engineergit clone --depth 1 https://github.com/heggria/taskflowWhat 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.00012 | $0.00320 |
| Opus 5 | $0.00006 | $0.00160 |
| Sonnet 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 yesterday.
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.
- yesterday First seen · 33 lines · 12 tokens per session scan A c786305d8307
test-engineer is an agent published in the GitHub repository heggria/taskflow (67 stars, last pushed 5d ago), licensed MIT. It adds 12 tokens to every session and 320 once invoked, about $0.0001 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-30.
Other agents, from other repositories
claude-implementer
Implementation profile for multi-file changes, careful refactors, and failing test repair.
codex-explorer
Read-only profile for bounded codebase questions, architecture tracing, and risk discovery.
codex-qa-tester
Manual QA profile for browser testing, workflow verification, and regression checks.
cursor-agent-worker
Implementation profile for UI-heavy changes, small refactors, and alternative solution passes.
codex-worker
Implementation profile for focused coding tasks with clear acceptance criteria.
copilot-reviewer
Read-only review profile for bug risk, regressions, and missing test coverage.