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.
npx skills add babyworm/rtl-agent-team --skill rtl-p4-implementgit 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/skills/babyworm/rtl-agent-team/rtl-p4-implement)<a href="https://agentmods.dev/skills/babyworm/rtl-agent-team/rtl-p4-implement"><img src="https://agentmods.dev/badge/skills/babyworm/rtl-agent-team/rtl-p4-implement/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/skills/babyworm/rtl-agent-team/rtl-p4-implement"><img src="https://agentmods.dev/badge/skills/babyworm/rtl-agent-team/rtl-p4-implement.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.00043 | $0.00633 |
| Opus 5.5 | $0.00017 | $0.00253 |
| Sonnet 5.5 | $0.00009 | $0.00127 |
| Haiku 4.5 | $0.00004 | $0.00063 |
Grade A, and why
rtl-p4-implement 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 18d 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<Use_When>
- Phase 3 μArch specs are complete and RTL coding is needed
- User says "implement RTL", "write RTL", "Phase 4", "code modules"
- Need lint-clean, unit-tested SystemVerilog modules
- Need the full 10-Wave implementation pipeline with comprehensive review/fix/refactor
- Need richer Phase-4 artifacts before handoff to Phase 5 </Use_When>
<Do_Not_Use_When>
- Phase 3 μArch specs are not complete (run rtl-p3-uarch-design first)
- Only need a single module bug fix (use rtl-p4s-bugfix)
- Need RTL + verification together from uarch (use rat-p4p5-impl-verify)
- Need a faster minimal Phase-4 sanity loop first (use rtl-p4-rapid-impl) </Do_Not_Use_When>
Prerequisites
Phase 3 completion required:
- At least one μArch spec in
docs/phase-3-uarch/must exist
If prerequisite is missing: WARNING — recommend running /rtl-agent-team:rtl-p3-uarch-design.
Proceed with available artifacts — orchestrator will adapt scope.
Execution
Task(subagent_type="rtl-agent-team:p4-implement-orchestrator", prompt="Execute Phase 4 RTL implementation. User input: $ARGUMENTS")
Do not perform any work directly. The orchestrator agent manages module enumeration, 10-Wave sequencing, parallel task dispatch, and phase gate verification.
Compliance Notes
- After each implementation wave completes (lint + unit test), invoke compliance-checker against P1+P2+P3 iron requirements
- RTL implementation must comply with all upstream iron requirements
- Per-wave compliance ensures regressions are caught before the integration gate (W10)
- Wave 0 includes test plan generation (Step 0b) — test scenarios are derived from uarch spec before RTL implementation begins, following TDD principles.
Output
rtl/*/*.sv— lint-clean SystemVerilog modulessim/*/tb_*.sv— per-module unit test testbenchesdocs/phase-4-rtl/— Stream B design documents and implementation summaryreviews/phase-4-rtl/— lint reports, code review reports, and wave completion records
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.
- 18d ago First seen · 61 lines · 43 tokens per session scan A 18c3bbf87a4e
rtl-p4-implement is a skill published in the GitHub repository babyworm/rtl-agent-team (61 stars, last pushed 19d ago), licensed MIT. It adds 43 tokens to every session and 633 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-10-08.
Other skills, from other repositories
test-sqrl
Use when adding or updating tests for a DataSQRL pipeline. Use after implementing features to verify correctness.
embedded-testing-patterns
Firmware test patterns with Unity, CMock, Ceedling, and QEMU: project layout, testable HAL interfaces, CMock expect chaining, error-path tests, and an on-target test runner over ITM. Use when making embedded C testable or writing tests for it.
mavlink-integration
Use this skill when a task involves MAVLink protocol communication via pymavlink, UART/UDP/TCP drone connections, ArduPilot SITL simulation, or telemetry message parsing in the edge service. Don't use it for raw UART hardware driver code without MAVLink framing (use embedded-systems), WebSocket transport to the web…
codexkit-test-hardening
Strengthen test coverage around changed behavior, edge cases, and regressions without writing noisy or brittle tests.
testing-business-rules
Use when adding, reviewing, or deleting tests, deciding whether a function needs coverage, or when a suite enumerates branches, signs, empty values, or implementation steps without naming the behavior at risk.
precommit
Run the deterministic pre-commit pipeline in fast or full mode through the packaged runner. Use when handing off repository changes. Not for: ad hoc replacement checks, dependency audits, or read-only verification. Output: runner-owned changed-file reporting and final verdict.