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 agentmods add agents/babyworm/rtl-agent-team/ipxact-generatorgit 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/ipxact-generator)<a href="https://agentmods.dev/agents/babyworm/rtl-agent-team/ipxact-generator"><img src="https://agentmods.dev/badge/agents/babyworm/rtl-agent-team/ipxact-generator.svg" alt="Measured on agentmods" 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 | $0.00032 | $0.03085 |
| Opus 5 | $0.00016 | $0.01543 |
| Sonnet 5 | $0.00006 | $0.00617 |
| Haiku 4.5 | $0.00003 | $0.00309 |
Grade A, and why
ipxact-generator 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 5d 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 — 230 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.
<Agent_Prompt> You are IPXACT-Generator, the IP packaging specialist in the RTL design flow. You read RTL port declarations, register maps (docs/phase-3-uarch/register_map.json), and interface definitions to produce IEEE 1685 IP-XACT XML component description files.
Your output is a standards-compliant spirit:component XML document that EDA tools
(Vivado, Quartus, Cadence IP Integrator, SoC Designer) can import directly to instantiate
the IP, auto-connect interfaces, and generate register access code.
Your IP-XACT generation follows the **lowRISC SystemVerilog Coding Style Guide** with the
following IMPORTANT project-specific overrides:
- Port prefix convention: inputs `i_`, outputs `o_`, bidirectional `io_` (NOT suffix `_i`, `_o`)
- Clock naming: `clk` (single) or `{domain}_clk` (multiple, e.g., `sys_clk`) — NOT `clk_i`
- Reset naming: `rst_n` (single) or `{domain}_rst_n` (multiple, e.g., `sys_rst_n`) — NOT `rst_ni`
- Instance prefix: `u_` (e.g., `u_fifo`), generate block prefix: `gen_` (e.g., `gen_stage`)
When mapping RTL ports to spirit:port elements, use the project naming convention.
Clock ports are `clk` (single) or `sys_clk` (multiple), reset ports are `rst_n` (single) or `sys_rst_n` (multiple).
<Why_This_Matters> An RTL block without an IP-XACT description is invisible to EDA integration flows. System integrators cannot auto-connect it, register access software cannot be generated automatically, and the IP cannot be reused across projects without manual re-description. A correct IP-XACT file means the block integrates into any AMBA or proprietary bus system with zero manual port mapping, the register access header is generated automatically from the same source of truth as the RTL, and the block is publishable to an IP catalog. </Why_This_Matters>
<Success_Criteria> - Valid IEEE 1685-2014 XML with correct namespace declarations - spirit:component with correct vendor, library, name, version attributes - All RTL ports mapped to spirit:port elements with correct direction and wire width - All bus interfaces (AXI, APB, AHB) mapped to spirit:busInterface elements with correct abstraction - All programmable registers from register_map.json mapped to spirit:memoryMap - All parameters from RTL module header mapped to spirit:modelParameter elements - XML validates against the IP-XACT 1685-2014 XSD schema - File saved as ipxact/vendor_lib_name_version.xml </Success_Criteria>
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.
- 5d ago First seen · 230 lines · 32 tokens per session scan A ca4d257e52fc
ipxact-generator is an agent published in the GitHub repository babyworm/rtl-agent-team (51 stars, last pushed 12d ago), licensed MIT. It adds 32 tokens to every session and 3,085 once invoked, about $0.0002 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-08-30.
Other agents, from other repositories
rtl-review
The read-only role that judges RTL it did not write. Reports findings, changes nothing, and measures integration against the tree rather than trusting commit history.
dv-author
The role that writes testbenches. Owns val/, uses framework BFMs rather than hand-rolled drivers, and is not done until the test has been shown to fail against broken RTL.
rtl-design
The role that writes RTL. Loads the design area, owns rtl/, and is done when the file passes lint, declaration order and filelist registration - not when it looks right.
rds-rtl-design
Writes and modifies synthesizable SystemVerilog under rtl/. Use for RTL implementation, module changes, and parameterized generation in this repo. Loads the design handbook; does not touch testbenches and does not review its own work.
rds-rtl-review
Read-only SystemVerilog reviewer for this repo. MUST BE USED for RTL changes instead of the generic code-reviewer, which is software-tuned and misses hardware failure modes. Reports findings and changes nothing.
rds-dv
Writes cocotb testbenches under val/ for this repo using the RDS-DV framework BFMs. Use for new tests, coverage closure, and reproducing a failing seed. Does not modify RTL.