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 bfm-developgit 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/bfm-develop)<a href="https://agentmods.dev/skills/babyworm/rtl-agent-team/bfm-develop"><img src="https://agentmods.dev/badge/skills/babyworm/rtl-agent-team/bfm-develop.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00053 | $0.02096 |
| Opus 5 | $0.00026 | $0.01048 |
| Sonnet 5 | $0.00011 | $0.00419 |
| Haiku 4.5 | $0.00005 | $0.00210 |
Grade A, and why
bfm-develop 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 4d 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<Use_When>
- Phase 2 artifacts (
docs/phase-2-architecture/architecture.md,refc/) are complete. - TLM models are needed for early performance estimation or protocol verification.
- BFM is needed as stimulus/checker in a verification environment.
- AMBA bus protocol modeling (AXI/AHB/APB) is required.
- DPI-C co-simulation interface is needed for SystemVerilog testbenches. </Use_When>
<Do_Not_Use_When>
- Architecture is not yet stable — a BFM built on a changing arch spec requires full rewrite.
- Only simple unit tests are needed → use
rtl-p4s-unit-testdirectly. - Pure software development without hardware interaction. </Do_Not_Use_When>
<Why_This_Exists>
TLM models run orders of magnitude faster than RTL simulation, enabling early detection of protocol bugs and performance bottlenecks before RTL exists. The BFM also serves as the performance reference in rtl-p5s-perf-verify. LT transport is the default because it gives fast functional validation; AT non-blocking is reserved for timing-accurate pipelined modeling.
</Why_This_Exists>
Prerequisites
docs/phase-2-architecture/architecture.mdandio_definition.jsonpresent.refc/reference model built (needed for cross-phase functional consistency check).- SystemC 3.0+ and ARM AMBA-PV headers installed.
If missing: WARNING — proceed with available artifacts; note absent dependencies in smoke test result.
<Responsibility_Boundary>
- Scripts handle build (
cmake/make) and smoke-test execution via Bash CLI. - LLM handles TLM module design, protocol binding, and feature-coverage mapping.
- Contract surface: port names must match
io_definition.jsonexactly; functional output must matchrefc/on shared test vectors. </Responsibility_Boundary>
What ships with it
10 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- examples/axi_stream_stub/Makefile 953 B
- examples/axi_stream_stub/src/axi_stream_stub_bfm.cpp 2.4 KB
- examples/README.md 2.2 KB
- examples/selfcheck_fake_build/.gitignore 125 B
- examples/selfcheck_fake_build/expected_run_report.json 557 B
- examples/selfcheck_fake_build/Makefile 718 B
- references/.gitkeep 0 B
- references/bfm-conventions.md 3.3 KB
- scripts/run_bfm.py 11 KB runs code
- templates/bfm_module_template.h 4.7 KB
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.
- 4d ago First seen · 131 lines · 53 tokens per session scan A e07ba4044624
bfm-develop is a skill published in the GitHub repository babyworm/rtl-agent-team (51 stars, last pushed 14d ago), licensed MIT. It adds 53 tokens to every session and 2,096 once invoked, about $0.0003 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
tuyaopen/usr-board
A workflow for adding a custom peripheral to a TuyaOpen project without changing the software development kit. A peripheral is an attached hardware device, and a TDD is a hardware driver interface used to control it.
vtestgen
Scaffold a Makefile-driven, CPU-bus-controlled testbench project for an IP and generate a comprehensive set of self-checking testcases, validate each with make, and write a testcase list.
vtestrun
Run all IP-level testcases from tclist.md through the bench Makefile, capture results, and write per-failure issue reports with no fix suggestions.
Verification & Quality Assurance
Comprehensive truth scoring, code quality verification, and automatic rollback system with 0.95 accuracy threshold for ensuring high-quality agent outputs and codebase reliability.
agent-optimization
Improve an Agent State through versioned scores and score-linked Traces from a frozen Benchmark.
holohub-app-lifecycle
Use for non-failing HoloHub app work with ./holohub: scaffold, build, run, test, visual evidence, lint, and flow benchmarking.