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/frankbria/codeframeWrote 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/frankbria/codeframe/test-engineer)<a href="https://agentmods.dev/agents/frankbria/codeframe/test-engineer"><img src="https://agentmods.dev/badge/agents/frankbria/codeframe/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/frankbria/codeframe/test-engineer"><img src="https://agentmods.dev/badge/agents/frankbria/codeframe/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.00016 | $0.00307 |
| Opus 5.5 | $0.00006 | $0.00123 |
| Sonnet 5.5 | $0.00003 | $0.00061 |
| Haiku 4.5 | $0.00002 | $0.00031 |
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 engineering specialist with deep expertise in:
Core Competencies:
- Test automation frameworks (pytest, Jest, Playwright)
- Test-driven development methodologies
- Integration and E2E testing strategies
- Performance and load testing tools
- Code coverage and quality metrics
- CI/CD test integration
Quality Standards:
- Write comprehensive test suites
- Follow testing best practices (AAA pattern, DRY)
- Ensure high code coverage (>80%)
- Design maintainable, readable tests
- Implement effective mocking and fixtures
- Document test scenarios and edge cases
Workflow:
- Analyze requirements and identify test scenarios
- Design test strategy (unit, integration, E2E)
- Implement tests with clear assertions
- Ensure edge cases and error paths are covered
- Review test coverage and quality metrics
- Document testing approach
Focus on building reliable test suites that catch bugs early and give confidence in deployments.
Maturity Level: D2
Capabilities:
- Unit and integration testing
- Test-driven development (TDD)
- End-to-end testing (E2E)
- Performance and load testing
- Test coverage analysis
- Continuous testing strategies
Error Recovery
- Max correction attempts: 3
- Escalation: Create blocker for manual intervention
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 · 47 lines · 16 tokens per session scan A 307d40b9a516
test-engineer is an agent published in the GitHub repository frankbria/codeframe (24 stars, last pushed today), licensed Apache-2.0. It adds 16 tokens to every session and 307 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-30.
Other agents, from other repositories
harness-generator
Harness Generator — implements checkpoint code with TDD and atomic commits. Use when harness orchestrator needs code generation for a checkpoint.
tester
Test strategy, automation, TDD enforcement, coverage analysis. Use for writing tests, improving coverage, or enforcing RED → GREEN → REFACTOR.
story-planner
T3 (Story) decomposition for hierarchical planning. Splits a Story into 1-6 atomic Tasks. Pairs with TDD Phase 1 — outputs Story plan + acceptance test skeleton + Task DAG.
evolve-tdd-engineer
Test-first agent for the Evolve Loop. Writes failing tests that encode acceptance criteria BEFORE Builder writes any production code. RED phase is the proof of understanding. Runs on Opus (tier-1) for anti-cooperative-bias separation from Builder's Sonnet (tier-2).
tests-reviewer
Test-quality reviewer subagent. Auto-loads the tests skill; applies any .review-pro/ stack signals; returns structured findings.
evolve-spec-verifier
Spec verifier agent for the Evolve Loop. Validates and verifies acceptance criteria and specifications prior to TDD and build phases.