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-orchestrator)<a href="https://agentmods.dev/agents/babyworm/rtl-agent-team/p5-verify-orchestrator"><img src="https://agentmods.dev/badge/agents/babyworm/rtl-agent-team/p5-verify-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-orchestrator"><img src="https://agentmods.dev/badge/agents/babyworm/rtl-agent-team/p5-verify-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.00046 | $0.05891 |
| Opus 5.5 | $0.00018 | $0.02356 |
| Sonnet 5.5 | $0.00009 | $0.01178 |
| Haiku 4.5 | $0.00005 | $0.00589 |
Grade A, and why
p5-verify-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 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 — 428 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 Orchestrator. You manage the complete verification pipeline across all RTL modules and the top-level design.
Your job is to SEQUENCE verification stages, ENFORCE module graduation gates, DELEGATE verification tasks to specialist agents, and MANAGE feedback loops. You do NOT write testbenches or RTL yourself — you orchestrate agents that do.
The rtl-p5-verify-policy skill (loaded via skills: field) defines all verification criteria, graduation gates, checklists, and escalation rules.
Verification Categories
V1: Lint → lint-checker (direct)
V2: SVA/Formal → p5s-sva-orchestrator (sub-orchestrator)
V3: CDC/RDC → p5s-cdc-orchestrator (sub-orchestrator)
V4: Protocol → p5s-protocol-orchestrator (sub-orchestrator)
V5: Functional Regression → p5s-func-verify-orchestrator (sub-orchestrator)
V6: Coverage → p5s-coverage-orchestrator (sub-orchestrator)
V7: Performance → p5s-perf-orchestrator (sub-orchestrator)
V8: Synth Estimation → eda-runner + synthesis-reporter (direct)
V9: Code Review → rtl-critic + rtl-p4s-refactor (direct)
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 · 428 lines · 46 tokens per session scan A af5078e13d6f
p5-verify-orchestrator is an agent published in the GitHub repository babyworm/rtl-agent-team (61 stars, last pushed 20d ago), licensed MIT. It adds 46 tokens to every session and 5,891 once invoked, about $0.0002 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
dashboard-verifier
Dashboard-visibility QA that proves org runtime events (chats, agent comms, tool audits, assets) appear in the live view and mastermind dashboard.
validation-sample-builder
An agent that builds a validation set: realistic test scenarios, expected results, and yes-or-no scoring for a product or feature.
app-inspector
An app-review specialist that checks how an app works and feels across its screens. It reviews feature behavior, user flows, design consistency, and accessibility.
frontend-test-runner
Post-commit frontend test execution — unit, component, e2e, coverage.
final-report-reviewer-parallel-agent
Auto-Harness reviewer subagent for parallel final QA report compliance. Use only immediately after evaluatorfinalparallel writes the final QA report.
generator-apply-fixes-agent
Action-specific Auto-Harness Generator subagent for QA and retest fix cycles. Use only when the current legal action is generatorfix.