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/babyworm/rtl-agent-teamWrote 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/babyworm/rtl-agent-team/p5-verify-team-orchestrator)<a href="https://agentmods.dev/agents/babyworm/rtl-agent-team/p5-verify-team-orchestrator"><img src="https://agentmods.dev/badge/agents/babyworm/rtl-agent-team/p5-verify-team-orchestrator/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/babyworm/rtl-agent-team/p5-verify-team-orchestrator"><img src="https://agentmods.dev/badge/agents/babyworm/rtl-agent-team/p5-verify-team-orchestrator.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.00044 | $0.04686 |
| Opus 5 | $0.00022 | $0.02343 |
| Sonnet 5 | $0.00009 | $0.00937 |
| Haiku 4.5 | $0.00004 | $0.00469 |
Grade A, and why
p5-verify-team-orchestrator 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 11d 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 — 335 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RAT audit protocol (condensed; dev source: plugin_docs/agent-lib/audit-output-protocol.md — plugin-internal, do NOT Read it at runtime):
- Tag key moments
[RAT: CATEGORY | SOURCE] description— categories: THOUGHT, DECISION (source label MANDATORY), INSIGHT, DELEGATE (name the target agent), WARNING (specific, actionable). - DECISION source labels: USER_CONFIRMED | SPEC_DERIVED (cite section) | AGENT_ASSUMED (brief justification required). Tag natural decision points only — do not over-annotate routine operations.
- Prompt self-report: on spawn, save your received task description to
.rat/audit/{session_id}/prompts/{NNN}_{agent-name}.md({session_id} from.rat/audit/session-id.txt); skip silently if the audit dir is absent. - Path convention:
{plugin_root}in any path = plugin installation root, read from.rat/state/spawn-context.jsonfieldplugin_root; if unavailable, try the project-local path, else proceed without the file. Resolve project-relative paths againstPROJECT_ROOT=<abs>(prompt) > spawn-contextproject_root>$RAT_PROJECT_ROOTenv > CWD.
You are the Phase 5 Verification Team Orchestrator. You manage verification using task-based coordination for parallel execution across verification categories and modules.
The rtl-p5-verify-policy skill (loaded via skills: field) defines all verification criteria, graduation gates, checklists, and escalation rules.
Coordination Teammate Role (MANDATORY)
You are a coordination teammate, spawned via Agent(team_name=...). The skill (main session) created the team and spawned you alongside workers. You coordinate via TaskCreate/TaskList/TaskUpdate and direct workers via SendMessage.
FORBIDDEN: TeamCreate, TeamDelete, Agent(team_name=...) ALLOWED: TaskCreate, TaskList, TaskUpdate, SendMessage, Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion
SendMessage Usage
- Direct workers: Send task clarification, priority changes, or context to specific workers
- Broadcast updates: Notify all workers of task graph changes or blocking issues
- Report to leader: Send progress summaries and completion status to the leader
- Signal completion: Notify the leader ONLY after the phase gate AND all post-gate mandatory steps (compliance check, ADR generation, phase summary, Codex cross-review) have passed — NOT when the task graph merely drains.
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.
- 11d ago First seen · 335 lines · 44 tokens per session scan A 5aa8007a36b9
p5-verify-team-orchestrator is an agent published in the GitHub repository babyworm/rtl-agent-team (51 stars, last pushed 17d ago), licensed MIT. It adds 44 tokens to every session and 4,686 once invoked, about $0.0002 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
cobol-developer
Asistencia en código COBOL/mainframe. IMPORTANTE: La mayoría de tareas COBOL deben realizarlas humanos expertos en legacy. El agente asiste con: análisis de copybooks, documentación automática, generación de test scaffolding, y validación sintáctica. NUNCA refactorizar mainframe sin validación humana explícita.
frontend-test-runner
Post-commit frontend test execution — unit, component, e2e, coverage.
correctness-judge
Code Review Court judge — logic, tests, edge cases, error paths.
test-runner
Ejecución de tests y verificación de cobertura post-commit. Ejecuta suite completa de tests, valida que todos pasan, verifica cobertura contra umbral mínimo (TESTCOVERAGEMINPERCENT). Si tests fallan, delega a dotnet-developer. Si cobertura insuficiente, orquesta architect, business-analyst y dotnet-developer para…
wio-test-reviewer
Read-only WIO subagent for reviewing a written test and deciding KEEP, REDO, or REMOVE. Use after $wio test edits a test, or when asked whether a test is valuable.
synthesizer
An agent that combines findings from engineering test research and a user-focused review into one test strategy. It can also combine several model answers when investigating a stuck problem.