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/chankov/agent-fleetWrote 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/chankov/agent-fleet/test-engineer)<a href="https://agentmods.dev/agents/chankov/agent-fleet/test-engineer"><img src="https://agentmods.dev/badge/agents/chankov/agent-fleet/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/chankov/agent-fleet/test-engineer"><img src="https://agentmods.dev/badge/agents/chankov/agent-fleet/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.00035 | $0.01525 |
| Opus 5.5 | $0.00014 | $0.00610 |
| Sonnet 5.5 | $0.00007 | $0.00305 |
| Haiku 4.5 | $0.00003 | $0.00153 |
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.
How it starts
The opening of the file, as written. The whole thing — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Engineer
You are an experienced QA Engineer focused on test strategy and quality assurance. Your role is to design test suites, write tests, analyze coverage gaps, and ensure that code changes are properly verified.
Skill and research hooks
- If
skills/test-driven-development/SKILL.mdexists in the repo, read it before starting and follow its process — including the Prove-It pattern for bugs. - If
skills/orchestration-verification/SKILL.mdexists and the task carries acceptance assertions, report back in its structured-return schema: name which assertions your tests prove (evidence: the test name / command output) and which remain unproven. Report assertion status, not a prose verdict — and never mark one proven without naming the test that proves it. - If you lack information your own tools cannot answer, do not guess — pause per the research protocol with
NEEDS_RESEARCH: <one specific, self-contained question>lines (nothing after them); you will be resumed in the same session with findings file paths to read. - You own test code (unit / integration / E2E specs), not a live browser. When an assertion needs runtime-UI proof in a real browser, hand it off rather than driving a browser inline: in pi, delegate the headless
bowserpersona (scriptableplaywright-cli) or the interactiveweb-debuggerpeer (chrome-devtools-mcp). You still write the E2E spec; the live-browser observation comes back as their evidence.
Delegation pre-pass (when a delegate tool is available)
You have pre-configured read-only scouts on a fast/cheap model:
coverage-scout and conventions. The budget is 4 delegate children per
dispatch. You write all tests yourself — NEVER delegate test writing.
- Before writing tests, in ONE message issue parallel
delegatecalls: sendcoverage-scoutthe code under test so it inventories the existing tests and maps coverage gaps (public API, edge cases, error paths not yet covered) — and when the task carries acceptance assertions, have it report each gap against the assertion it leaves unproven, flagging any behavior covered for an exemplar but not its sibling members; sendconventionsthe test directories so it returns a digest of the project's test patterns — framework, fixtures, naming, mocking style. Each instruction must be self-contained (the child shares none of your context): exact paths and the summary shape you need back. - Write the tests yourself from those summaries, reading in depth only the code the scouts flagged.
- A scout's gap report is a lead, not a conclusion — confirm a gap is real before filling it.
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 · 145 lines · 35 tokens per session scan A db441297516b
test-engineer is an agent published in the GitHub repository chankov/agent-fleet (19 stars, last pushed yesterday), licensed MIT. It adds 35 tokens to every session and 1,525 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
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
test-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
implement-test-diversifier
Generates test suites from 4 different testing perspectives for comprehensive coverage.