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-p3-uarch-policygit 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-p3-uarch-policy)<a href="https://agentmods.dev/skills/babyworm/rtl-agent-team/rtl-p3-uarch-policy"><img src="https://agentmods.dev/badge/skills/babyworm/rtl-agent-team/rtl-p3-uarch-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.
<a href="https://agentmods.dev/skills/babyworm/rtl-agent-team/rtl-p3-uarch-policy"><img src="https://agentmods.dev/badge/skills/babyworm/rtl-agent-team/rtl-p3-uarch-policy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium analysis-evasion · line 1 Suspicious Unicode normalization or mixed-script contentFix: Review the flagged content for security risks. Ensure no credentials, secrets, or sensitive data are exposed.
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.00024 | $0.04897 |
| Opus 5 | $0.00012 | $0.02448 |
| Sonnet 5 | $0.00005 | $0.00979 |
| Haiku 4.5 | $0.00002 | $0.00490 |
Grade A, and why
rtl-p3-uarch-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.
How it starts
The opening of the file, as written. The whole thing — 364 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Phase 3 μArch Design Policy
Document Requirements (per-module docs/phase-3-uarch/*.md)
Each module document MUST contain:
- Module decomposition: sub-modules with rationale (or single-module rationale)
- Clock domain assignment: per sub-block, with synchronizer specs for cross-domain
- Protocol assignment: per interface with justification (data rate, latency, backpressure)
- Design partitioning: pipeline stages, resource sharing, parallelism degree
- Register/SRAM/FSM allocation: pipeline regs, config regs, SRAM capacity+banking, FSM state count
- Inter/intra-module pipeline: data flow, handshake, backpressure, hazard analysis
- Signal naming: compliant with conventions below
REQ→uArch Reverse Traceability
Every P3 run MUST produce docs/phase-3-uarch/req-uarch-traceability.md mapping each requirement
from docs/phase-1-research/iron-requirements.json (REQ-F-, REQ-P-) and
docs/phase-2-architecture/iron-requirements.json (REQ-A-*) to the uArch module(s) and section(s) implementing it.
Format:
| REQ ID | uArch Module(s) | Section(s) | Status |
|----------|-------------------------|-----------------------------|----------|
| REQ-001 | intra_pred | 3.2 Mode Decision FSM | MAPPED |
| REQ-002 | deblock_filter, sao | 2.1 Pipeline, 4.3 SAO Ctrl | MAPPED |
| REQ-003 | — | — | UNMAPPED |
- 100% coverage required: every REQ-NNN must appear. UNMAPPED REQs block the Phase 3 gate.
- Staleness detection: when P1
iron-requirements.jsonchanges after P3 completion, this table identifies which uArch sections need re-design. The P3 orchestrator uses mtime comparison to detect staleness.
Clock Domain Assignment Rules
- Every sub-block MUST have an assigned clock domain
- Single-domain:
clk/rst_n - Multi-domain:
{domain}_clk/{domain}_rst_n(e.g.,sys_clk,pixel_clk) - Cross-domain interfaces: explicit synchronizer type (2FF, handshake, async FIFO)
- Clock domain map: documented per module (which blocks share clocks, which cross)
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.
- 8d ago First seen · 364 lines · 24 tokens per session scan A 9c81aa52a030
rtl-p3-uarch-policy is a skill published in the GitHub repository babyworm/rtl-agent-team (51 stars, last pushed 19d ago), licensed MIT. It adds 24 tokens to every session and 4,897 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
hardware-health-check
Out-of-band hardware health via Redfish BMC (read-only) — power state, component health, thermal and power readings, firmware inventory, SEL log triage. Use when determining whether a host is powered off versus unreachable, checking hardware faults, reviewing thermal or PSU state, or triaging BMC event logs.
readable-verilog-generator
Use when creating, writing, reviewing, annotating, repairing, refactoring, or validating readable Verilog RTL, including synthesizable Verilog-2001 .v files, existing-RTL analysis, semantic comment annotation, testbench scaffold planning, ASIC-quality review, local or remote Vivado/xsim validation, evidence-backed…
hardware-saas-gtm
🇺🇸 Hardware + SaaS GTM Playbook — End-to-end go-to-market for consumer hardware products with software subscription models. Covers crowdfunding engineering (Kickstarter/Indiegogo/Makuake), KOL matrix for physical products, hardware PMF validation metrics, device-as-funnel subscription design, localization entry…
step-parts
Find, evaluate, and download low-level common standard CAD parts from step.parts, such as screws, bolts, nuts, washers, bearings, standoffs, electronics parts, motors, connectors, and other off-the-shelf components. Use when Codex needs to search the hosted step.parts catalog, resolve fuzzy part names, standards…
system-info
A skill for checking computer hardware, system status, running processes, and available disk space.
hdldiagzero
Generate validated SVG block diagrams for HDL/RTL/FPGA/SoC designs. Use when asked to draw, diagram, sketch, render, or visualize Verilog, SystemVerilog, VHDL, Vivado BD, or LiteX architecture. Produces JSON specs plus SVGs, color-codes clock domains, distinguishes AXI/MM/Lite/Stream and TileLink, and hides…