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/uarch-to-verify-orchestrator)<a href="https://agentmods.dev/agents/babyworm/rtl-agent-team/uarch-to-verify-orchestrator"><img src="https://agentmods.dev/badge/agents/babyworm/rtl-agent-team/uarch-to-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/uarch-to-verify-orchestrator"><img src="https://agentmods.dev/badge/agents/babyworm/rtl-agent-team/uarch-to-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.00061 | $0.04575 |
| Opus 5.5 | $0.00024 | $0.01830 |
| Sonnet 5.5 | $0.00012 | $0.00915 |
| Haiku 4.5 | $0.00006 | $0.00458 |
Grade A, and why
uarch-to-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 — 367 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 μArch-to-Verify Orchestrator. You drive the RTL design pipeline through Phase 4 (RTL Implementation) and Phase 5 (Extensive Verification), using completed Phase 1-3 design documents as input.
Your job is to VERIFY prerequisites, SEQUENCE phases, ENFORCE gates, DELEGATE work to specialist agents, MANAGE feedback loops, and PERSIST state for resumability. You do NOT implement RTL or write verification code yourself — you orchestrate agents that do.
The rat-p4p5-impl-verify-policy skill (loaded via skills: field) defines all gate criteria, prerequisite checks, feedback classification, checklists, and escalation rules.
Workflow
Step 0: Context Bootstrap (MANDATORY)
Project root: resolve all project-relative paths (including .rat/...) via the first available of:
explicit PROJECT_ROOT=<abs> line in your spawning prompt > project_root field in .rat/state/spawn-context.json (authoritative when present) > $RAT_PROJECT_ROOT env > process CWD (legacy default).
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 · 367 lines · 61 tokens per session scan A 3496d9c7a5d5
uarch-to-verify-orchestrator is an agent published in the GitHub repository babyworm/rtl-agent-team (58 stars, last pushed 10d ago), licensed MIT. It adds 61 tokens to every session and 4,575 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-09-03.
Other agents, from other repositories
expert
Frontier-grade domain-authority evaluator. Checks an artifact's technical accuracy, completeness, and state-of-the-art currency against EXTERNAL authoritative sources — fetched from the open web, since a general model must ground domain claims rather than assert them. Top tier of the user-mastery spectrum (beginner →…
hub-persona-auditor
Use when an external-facing draft (briefing, card, guide) is ready for pre-publication audit. Returns 3+ persona reader simulation, 4-axis (resonance/confusion/resistance/supplement) review, and 3-tier revision proposals (mandatory/strong/recommended). Do not use for internal memos, CATALOG entries, memory files, code…
architect
A system-architecture agent that maps how a software project should be structured. It creates a simple first design and a more detailed version, including the main bottleneck—the part most likely to limit the system.
browser-tester
A browser-based end-to-end tester for checking user interfaces with Playwright, a tool that controls a real web browser. It starts the app, captures desktop and mobile screenshots, and reads what appears on screen.
dev-planner
A development-planning agent that turns a detailed software architecture into an ordered list of implementable features.
chief-backtrack
Backtrack CHIEF candidates from subtask to Agent to Step.