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/p4s-unit-test-orchestrator)<a href="https://agentmods.dev/agents/babyworm/rtl-agent-team/p4s-unit-test-orchestrator"><img src="https://agentmods.dev/badge/agents/babyworm/rtl-agent-team/p4s-unit-test-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/p4s-unit-test-orchestrator"><img src="https://agentmods.dev/badge/agents/babyworm/rtl-agent-team/p4s-unit-test-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.00050 | $0.02872 |
| Opus 5.5 | $0.00020 | $0.01149 |
| Sonnet 5.5 | $0.00010 | $0.00574 |
| Haiku 4.5 | $0.00005 | $0.00287 |
Grade A, and why
p4s-unit-test-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 — 224 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 2 Unit Test Orchestrator. You manage unit testing for each RTL module against its microarchitecture specification and C reference model.
Your job is to DELEGATE testbench writing to testbench-dev, SELECT the reference comparison mode, DELEGATE simulation to eda-runner, and TRIAGE failures with waveform-analyzer. You do NOT write testbenches or RTL yourself.
The rtl-p4s-unit-test-policy skill (loaded via skills: field) defines coding conventions, reference mode rules, result JSON schema, escalation rules, and the checklist.
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 · 224 lines · 50 tokens per session scan A eea77a742bc6
p4s-unit-test-orchestrator is an agent published in the GitHub repository babyworm/rtl-agent-team (61 stars, last pushed 18d ago), licensed MIT. It adds 50 tokens to every session and 2,872 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
embedded-test-engineer
Use this agent when adding tests to firmware: Unity and Ceedling unit tests, CMock hardware mocks, dependency injection so driver logic runs on the host, QEMU emulation, gcov coverage, or testing ISR logic without hardware. It designs the test architecture, the test cases, the build, and the coverage setup.
embedded-systems
Implement Raspberry Pi 5 edge code for the edge service -- UART, camera, GPIO, systemd, and MOCKMODE fallbacks.
mavlink-specialist
Implement MAVLink message parsing and generation, manage UART/UDP/TCP connections, and integrate with ArduPilot SITL for testing.
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.
test-engineer
Creación y ejecución de tests en proyectos .NET. Usar PROACTIVELY cuando: se escriben tests unitarios o de integración en xUnit/NUnit/MSTest, se configura TestContainers para tests con base de datos, se verifica cobertura de código, se detectan tests faltantes en una implementación, o se crea la estructura de un…
frontend-test-runner
Post-commit frontend test execution — unit, component, e2e, coverage.