OpenAgents Control is a framework that adds plan-first, approval-based coding workflows to OpenCode, an AI coding framework. Developers and teams use it to make agents follow shared coding patterns, work across several programming languages, and validate changes through testing and review. The catalogue includes its agents, skills, commands, plugin, and hook.
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/darrenhinde/OpenAgentsControlWrote 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/darrenhinde/openagentscontrol/test-engineer)<a href="https://agentmods.dev/agents/darrenhinde/openagentscontrol/test-engineer"><img src="https://agentmods.dev/badge/agents/darrenhinde/openagentscontrol/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/darrenhinde/openagentscontrol/test-engineer"><img src="https://agentmods.dev/badge/agents/darrenhinde/openagentscontrol/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.00019 | $0.02102 |
| Opus 5.5 | $0.00008 | $0.00841 |
| Sonnet 5.5 | $0.00004 | $0.00420 |
| Haiku 4.5 | $0.00002 | $0.00210 |
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 — 281 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TestEngineer
Mission: Author comprehensive tests following TDD principles — grounded in project testing standards pre-loaded by main agent.
Core Rules
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 · 281 lines · 19 tokens per session scan A d7d2899e9640
test-engineer is an agent published in the GitHub repository darrenhinde/OpenAgentsControl (4,910 stars, last pushed 1mo ago), licensed MIT. It adds 19 tokens to every session and 2,102 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
tdd-coach
Test-driven development specialist. Use when implementing features, bugfixes, or code changes to ensure the Red-Green-Refactor cycle is followed. Write tests first, watch them fail, then implement.
gem-implementer
TDD code implementation: features, bugs, refactoring. Never reviews own work.
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.
executor
Specialized agent for executing implementation plans. Reads plan, extracts Environment Context, runs tasks with TDD and checkpoints.
tl-test-writer
Team-loop test writer for a regulated work package. Works in its own git worktree and writes the package's tests from the spec and brief, independently of the builder, commits them alone and stops. Use at step 5 of the team loop for regulated packages only. Never writes implementation.
code-implementer
Implements code per an architecture document: TDD cycle, minimal changes, fail-fast. Activates the sdlc:code-implementer skill which references the tdd-master:tdd-master skill for the RED-GREEN-REFACTOR workflow and loads stack-specific implement references (backend-python / frontend-react) on demand. Never designs…