rtl-p5s-integration-test-policy

rtl-p5s-integration-test-policy is a skill for Claude Code from babyworm/rtl-agent-team. It costs 27 tokens per session (1,127 once invoked), scanned A, original, MIT.

An internal rule set for integration testbenches that connect several RTL modules. It specifies naming, signal types, test order, and the result format for connectivity, data flow, stalls, and recovery.

In plain words
What is it for?
Use it when writing or reviewing Tier 4 RTL integration tests. It covers reset and clock connections, port widths, normal transfers, throughput, backpressure, and error recovery.
Why use it?
Consistent testbench structure makes wiring and interface failures easier to detect and compare. The required order starts with fast connection checks before more involved traffic tests.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter.

Part of the rtl-agent-team plugin — 97 skills, 99 agents, 6 hooks shipped together

Good fit Use it when writing or reviewing Tier 4 RTL integration tests. It covers reset and clock connections, port widths, normal transfers, throughput, backpressure, and error recovery.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/babyworm/rtl-agent-team/rtl-p5s-integration-test-policy
Install

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.

Any agent
npx skills add babyworm/rtl-agent-team --skill rtl-p5s-integration-test-policy
Clone the repo
git clone --depth 1 https://github.com/babyworm/rtl-agent-team

Made for: Claude Code.

Or install rtl-agent-team, the plugin that ships this one along with the rest of its 97 skills, 99 agents, 6 hooks.

Wrote 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.

agentmods badge for rtl-p5s-integration-test-policy

README.md
[![agentmods](https://agentmods.dev/badge/skills/babyworm/rtl-agent-team/rtl-p5s-integration-test-policy/github.svg)](https://agentmods.dev/skills/babyworm/rtl-agent-team/rtl-p5s-integration-test-policy)
Your own site
<a href="https://agentmods.dev/skills/babyworm/rtl-agent-team/rtl-p5s-integration-test-policy"><img src="https://agentmods.dev/badge/skills/babyworm/rtl-agent-team/rtl-p5s-integration-test-policy/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.

agentmods 80×15 button for rtl-p5s-integration-test-policy

Your own site · 80×15
<a href="https://agentmods.dev/skills/babyworm/rtl-agent-team/rtl-p5s-integration-test-policy"><img src="https://agentmods.dev/badge/skills/babyworm/rtl-agent-team/rtl-p5s-integration-test-policy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 27 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,127 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00027 $0.01127
Opus 5.5 $0.00011 $0.00451
Sonnet 5.5 $0.00005 $0.00225
Haiku 4.5 $0.00003 $0.00113

Measured 8d ago against content hash 610c7dead4fd, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

rtl-p5s-integration-test-policy 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 8d 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.

skills/rtl-p5s-integration-test-policy/SKILL.md · 116 lines

How it starts

The opening of the file, as written. The whole thing — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Tier 4 Integration Test Policy

Coding Convention Requirements

Integration testbenches MUST follow project conventions:

  • Port connections: i_ prefix for inputs, o_ prefix for outputs
  • Clock: clk (single domain) or {domain}_clk (multiple, e.g., sys_clk) — NOT clk_i
  • Reset: rst_n (single domain) or {domain}_rst_n (multiple, e.g., sys_rst_n) — NOT rst_ni
  • DUT instance: u_dut for top-level, u_ prefix for sub-modules
  • Use logic only (NOT reg/wire)
  • cocotb signals: dut.sys_clk, dut.i_*, dut.o_*

Integration Test Ordering (mandatory sequence)

  1. Static connectivity checks first (fast, catches wiring bugs)
  2. Simple data flow (single transaction end-to-end)
  3. Sustained throughput (back-to-back transactions)
  4. Backpressure and stall scenarios
  5. Error injection and recovery

Result JSON Schema

{
  "top_module": "{top}",
  "tier": 4,
  "connectivity": {
    "reset_propagation": "PASS",
    "clock_connectivity": "PASS",
    "port_width_match": "PASS"
  },
  "data_flow": [
    {"scenario": "basic_forward", "status": "PASS", "req_ids": ["REQ-U-001"]},
    {"scenario": "max_throughput", "status": "PASS", "req_ids": ["REQ-U-007", "REQ-P-003"]}
  ],
  "handshake": [
    {"test": "backpressure_propagation", "status": "PASS", "req_ids": ["REQ-U-012"]},
    {"test": "pipeline_flush", "status": "PASS", "req_ids": ["REQ-U-015"]}
  ],
  "e2e_reference": "PASS",
  "verdict": "PASS"
}

Simulation Commands

SV TB:

scripts/run_sim.sh --sim verilator --top tb_{top}_integration \
  --filelist rtl/filelist_top.f --outdir sim/top --trace \
  sim/top/tb_{top}_integration.sv

cocotb:

make -C sim/top sim SIM=verilator TOPLEVEL={top} MODULE=test_{top}_integration

Fallback (iverilog):

scripts/run_sim.sh --sim iverilog --top tb_{top}_integration \
  --filelist rtl/filelist_top.f --outdir sim/top --trace \
  sim/top/tb_{top}_integration.sv

Multi-Clock Domain Integration

  • Verify CDC synchronizers are connected correctly
  • Test data transfer across clock domains
  • Use rtl-p5s-cdc-verify for detailed CDC analysis

Read the full file on GitHub · 116 lines

Changes

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.

  1. 8d ago First seen · 116 lines · 27 tokens per session scan A 610c7dead4fd

Subscribe to this mod's changes

rtl-p5s-integration-test-policy is a skill published in the GitHub repository babyworm/rtl-agent-team (57 stars, last pushed 9d ago), licensed MIT. It adds 27 tokens to every session and 1,127 once invoked, about $0.0001 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.

Related

Other skills, from other repositories

jetson-video-pipeline

Use when planning, executing, and independently validating Jetson Video Codec SDK or PyNvVideoCodec encode/decode, transcode, segmentation, container decode, AV1, or concise acceptance workflows.

NVIDIA/skills · 45 tokens

image-compare

Compare two image files on disk and report what changed, region by region. Trigger on "what changed between these two images", "diff these PNGs", "did this render drift", "compare screenshots/exports/renders".

teimurjan/blazediff · 49 tokens

local-test

Build, run, and test IronClaw locally using Docker containers and Chrome MCP browser automation.

suyoumo/ClawProBench · 22 tokens

browser-qa

Drive a real headless browser against a locally-served web UI and capture screenshot evidence, reporting step-level PASS/FAIL/BLOCKED with extracted DOM text and console errors. Use when a phase on the docker QA image must exercise a rendered UI and attach screenshots — it complements the text-evidence verify/qa-test…

nearform/lastlight · 69 tokens

qa-test

Run an automated QA flow against a CLI or a locally-served app and report step-level pass/fail with evidence. Use when asked to QA-test a feature, exercise a flow end-to-end, or smoke-test what a PR changed.

nearform/lastlight · 51 tokens

qp

QP (Quality Platform) router — takes a web URL or a desktop app name and runs the plan → run → regress loop (qp-plan, qp-run, qp-regress) end to end, or routes to one stage. Classifies the target (public vs profile-required), probes which adapter the session has (Playwright MCP for web, computer-use MCP for desktop)…

chrono-meta/forge-harness · 138 tokens