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-p4s-bugfixgit 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-p4s-bugfix)<a href="https://agentmods.dev/skills/babyworm/rtl-agent-team/rtl-p4s-bugfix"><img src="https://agentmods.dev/badge/skills/babyworm/rtl-agent-team/rtl-p4s-bugfix/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-p4s-bugfix"><img src="https://agentmods.dev/badge/skills/babyworm/rtl-agent-team/rtl-p4s-bugfix.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.00045 | $0.00619 |
| Opus 5.5 | $0.00018 | $0.00248 |
| Sonnet 5.5 | $0.00009 | $0.00124 |
| Haiku 4.5 | $0.00005 | $0.00062 |
Grade A, and why
rtl-p4s-bugfix 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Core principle: lint is only a syntax check, not evidence of functional correctness.
This skill integrates with the PostToolUse:Edit hook tracking system. Modified .sv files are automatically tracked, and session termination is blocked without functional verification.
<Use_When>
- Fixing RTL bugs found during Phase 4 review
- Fixing functional errors in RTL modules
- Adding or modifying functionality in existing RTL
- Verifying no functional regression after refactoring
- Fixing integration bugs spanning multiple modules
- Phase 5→4 Feedback Loop: Automatic fix path invoked when Phase 5 verification FAILs </Use_When>
<Do_Not_Use_When>
- Coding convention changes only (e.g., port renaming with no functional change) → use rtl-p4s-refactor
- Writing a new module from scratch → use rtl-p4-implement
- Simple lint error fixes (e.g., removing unused signals) → use rtl-lint-check </Do_Not_Use_When>
<Why_This_Exists> Born from a previous session where 9 RTL bugs were fixed with only lint runs, skipping TB/simulation entirely. Passing lint is merely "compilation success" — simulation is required to prove the fix is functionally correct.
Anti-pattern example:
- 312 lines of RTL modified across 5 Waves → only verilator --lint-only executed → 0 TBs, 0 simulations
- Result: declared "complete" with zero functional correctness verification </Why_This_Exists>
All policies, checklists, escalation rules, and parallel fix decision logic are defined in the rtl-p4s-bugfix-policy skill (loaded via the orchestrator's skills: field).
Execution
Task(subagent_type="rtl-agent-team:p4s-bugfix-orchestrator", prompt="Execute RTL bug fix cycle. Bug description: $ARGUMENTS")
Do not perform any work directly. The orchestrator agent manages the full analyze → fix → lint → TB → simulation cycle.
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 · 62 lines · 45 tokens per session scan A 8b11f6e936a8
rtl-p4s-bugfix is a skill published in the GitHub repository babyworm/rtl-agent-team (61 stars, last pushed 19d ago), licensed MIT. It adds 45 tokens to every session and 619 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
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.
boot-doctor-mcp
Deterministic PC no-boot / no-POST / no-display troubleshooting — real BIOS beep-code lookup and a ranked next-steps engine, no LLM guessing at hardware causes. Use this whenever the user describes a computer that won't turn on, won't POST, has no display output, is beeping, or asks for hardware troubleshooting steps…
fpga-hardware-design-and-review-guide
Comprehensive FPGA hardware design guide based on real-world project experience. Covers pipeline architecture, timing optimization, SystemVerilog coding patterns, CDC handling, and practical debugging techniques. Use this skill when: (1) designing FPGA modules with timing constraints, (2) implementing video processing…
vdebug
Trace failing signals through the RTL hierarchy, classify root cause, and write a debug report per issue — no fix is proposed.
gke-ai-troubleshooting-tpu-dynamic-slices-monitoring
Monitors, troubleshoots, and manages GKE TPU Dynamic Slices custom resources. Use when checking TPU slice lifecycle states, troubleshooting slice provisioning failures, validating single-slice or multi-slice (JobSet) workload manifests, or safely patching stuck finalizers and disabling the slice controller. Don't use…
gke-ai-troubleshooting-tpu-vbar-oom
Diagnoses and prevents vbarcontrolagent segfaults, out-of-memory (OOM) errors, and TPU device initialization failures on TPU v6e nodes in GKE caused by race conditions during TPU device resets or high-frequency metrics polling. Use when troubleshooting vbarcontrolagent crashes, memory cgroup OOMs in serial console…