Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/babyworm/rtl-agent-teamnpx agentmods add agents/babyworm/rtl-agent-team/p5s-uvm-orchestratorWrote 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/p5s-uvm-orchestrator)<a href="https://agentmods.dev/agents/babyworm/rtl-agent-team/p5s-uvm-orchestrator"><img src="https://agentmods.dev/badge/agents/babyworm/rtl-agent-team/p5s-uvm-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/p5s-uvm-orchestrator"><img src="https://agentmods.dev/badge/agents/babyworm/rtl-agent-team/p5s-uvm-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.00076 | $0.04179 |
| Opus 5.5 | $0.00030 | $0.01672 |
| Sonnet 5.5 | $0.00015 | $0.00836 |
| Haiku 4.5 | $0.00008 | $0.00418 |
Grade A, and why
p5s-uvm-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 — 338 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 UVM Verification Orchestrator. You drive commercial simulator availability checking, UVM environment generation, compilation, test execution, and coverage collection.
Your job is to ENFORCE the hard simulator gate, DELEGATE UVM environment writing to testbench-dev, DISPATCH compilation and simulation runs to eda-runner, and INVOKE waveform-analyzer on failures. You do NOT write UVM code or run simulations yourself.
The rtl-p5s-uvm-policy skill (loaded via skills: field) defines UVM class hierarchy, component naming conventions, simulator-specific compile flags, coverage collection commands, and escalation conditions.
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 · 338 lines · 76 tokens per session scan A d87cf63e94f3
p5s-uvm-orchestrator is an agent published in the GitHub repository babyworm/rtl-agent-team (61 stars, last pushed 18d ago), licensed MIT. It adds 76 tokens to every session and 4,179 once invoked, about $0.0003 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
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.
chip-env-writer
A specialised coding agent for building chip verification environments with SystemVerilog and UVM 1.2. UVM is a standard framework for testing hardware designs, while BDD describes expected behaviour as Given, When, and Then scenarios.
chip-sw-verifier
A chip-software testing role for checking hardware drivers and firmware on bare-metal systems, Linux, or real-time operating systems. It can create test plans, unit and integration tests, hardware mocks, and coverage reports.
climate-test-engineer
Automotive climate test engineer validating vehicle system performance across environmental conditions.
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.
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.