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-sva-orchestrator)<a href="https://agentmods.dev/agents/babyworm/rtl-agent-team/p5s-sva-orchestrator"><img src="https://agentmods.dev/badge/agents/babyworm/rtl-agent-team/p5s-sva-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-sva-orchestrator"><img src="https://agentmods.dev/badge/agents/babyworm/rtl-agent-team/p5s-sva-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.00056 | $0.02617 |
| Opus 5 | $0.00028 | $0.01308 |
| Sonnet 5 | $0.00011 | $0.00523 |
| Haiku 4.5 | $0.00006 | $0.00262 |
Grade A, and why
p5s-sva-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 — 199 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 SVA/Formal Verification Orchestrator. You drive formal property extraction, iterative refinement, and SymbiYosys proof execution across all RTL modules.
Your job is to DELEGATE property extraction to sva-extractor, DISPATCH BMC/prove/cover runs to eda-runner, TRACK task-level PASS/FAIL/TIMEOUT status, and INVOKE waveform-analyzer on counterexamples. You do NOT write SVA properties or RTL yourself.
The rtl-p5s-sva-policy skill (loaded via skills: field) defines SVA coding conventions, engine selection guide, iterative refinement rules, 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.
- 11d ago First seen · 199 lines · 56 tokens per session scan A d1a9910a7cea
p5s-sva-orchestrator is an agent published in the GitHub repository babyworm/rtl-agent-team (51 stars, last pushed 17d ago), licensed MIT. It adds 56 tokens to every session and 2,617 once invoked, about $0.0003 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.
benchmark-agent
Runs Vibe-IC benchmark campaigns — "Run Benchmark Evaluation" (open benchmarks: VerilogEval / RTLLM / CVDP via /vibe-ic-benchmark) and "Benchmark IC" (the canonical ICs via /vibe-ic-all → /benchmark-verify). Commits + pushes results under benchmark-data/. When it finds a chip-AGNOSTIC plugin/MCP gap it AUTHORS the fix…
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.