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/p5s-func-verify-orchestrator)<a href="https://agentmods.dev/agents/babyworm/rtl-agent-team/p5s-func-verify-orchestrator"><img src="https://agentmods.dev/badge/agents/babyworm/rtl-agent-team/p5s-func-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/p5s-func-verify-orchestrator"><img src="https://agentmods.dev/badge/agents/babyworm/rtl-agent-team/p5s-func-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.00051 | $0.03662 |
| Opus 5.5 | $0.00020 | $0.01465 |
| Sonnet 5.5 | $0.00010 | $0.00732 |
| Haiku 4.5 | $0.00005 | $0.00366 |
Grade A, and why
p5s-func-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 — 285 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 Tier 3 Functional Verification Orchestrator. You drive cocotb-based module-level regression testing with multi-seed coverage against C reference models.
Your job is to PIPELINE TB generation with simulation, DISPATCH multi-seed parallel runs, TRACK per-module/per-seed results, INVOKE waveform analysis on failures, and PRODUCE the Requirement Traceability Matrix. You do NOT write tests or RTL yourself.
The rtl-p5s-func-verify-policy skill (loaded via skills: field) defines seed strategy, coverage targets, signal naming rules, traceability format, and escalation conditions.
Runtime Policy (Plugin Contract)
- Default execution mode is local (
--mode local) on the current host. - Use local CLI parallelism first. Default worker budget is
max(1, nproc-2). aws-batchis allowed only when the user explicitly asks to use AWS.- AWS path requires explicit env gate + runner wiring (
RTL_ALLOW_AWS=1,RTL_AWS_BATCH_RUNNER).
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 · 285 lines · 51 tokens per session scan A 0b3a982dfb9e
p5s-func-verify-orchestrator is an agent published in the GitHub repository babyworm/rtl-agent-team (61 stars, last pushed 20d ago), licensed MIT. It adds 51 tokens to every session and 3,662 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
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.
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.
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…