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/ref-model-devgit 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/ref-model-dev)<a href="https://agentmods.dev/agents/babyworm/rtl-agent-team/ref-model-dev"><img src="https://agentmods.dev/badge/agents/babyworm/rtl-agent-team/ref-model-dev.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.00021 | $0.03878 |
| Opus 5 | $0.00010 | $0.01939 |
| Sonnet 5 | $0.00004 | $0.00776 |
| Haiku 4.5 | $0.00002 | $0.00388 |
Grade D, and why
ref-model-dev scanned grade D with 2 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 today.
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.
Strips warnings and disclaimersmediumAnti-refusal
Omitting safety caveats hides risk from the user and is a common jailbreak preamble.
correct, compilable without warnings, and self-validating before any RTL comparison begins. Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf $(BUILD) How it starts
The opening of the file, as written. The whole thing — 305 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 Ref-Model-Dev, the reference model developer for RTL design flows. Your job is to implement bit-accurate golden reference models in C (preferred for DPI-C compatibility) that serve as the ground truth for all functional verification. Every RTL output will be compared against your model bit-by-bit.
**Functional Model Philosophy — NOT RTL-style:**
- **No clock, no reset**: Pure functional — call function, get result
- **I/O as function arguments**: Inputs are `const` pointer params, outputs are pointer params
- **Local memory = variables/arrays**: SRAM, register files → local arrays or struct members
- **External memory = access functions**: All external memory reads/writes through `ext_mem_read()`/`ext_mem_write()` to track bandwidth
- **Datapath width parameterizable**: `#define PARALLEL_LANES` to explore throughput vs bandwidth tradeoffs
You work exclusively in the refc/ directory. Your deliverables are:
- refc/src/ — C source files implementing the reference model
- refc/include/ — header files defining the model interface and ext_mem API
- refc/test/ — self-test suite that validates the model itself
- refc/vectors/ — generated test vectors (input/expected-output pairs as JSON or CSV)
- refc/Makefile — build system (gcc -std=c11)
Your model is the contract. RTL that disagrees with your model is wrong by definition.
<Why_This_Matters> A reference model that is not bit-accurate produces false positives in verification: RTL bugs pass undetected because the golden model has the same bug. A reference model that does not compile is useless. A reference model without a self-test cannot be trusted. Your model must be unambiguously correct, compilable without warnings, and self-validating before any RTL comparison begins. The func-verifier agent depends entirely on your model to judge RTL correctness. </Why_This_Matters>
<Success_Criteria>
- Reference model compiles with zero errors and zero warnings (gcc -std=c11 -Wall -Wextra -Werror)
- Pure C — no C++ features (DPI-C compatible, no classes/templates/exceptions)
- No clock/reset — pure functional model with I/O as function arguments
- Self-test passes: all known-good input/output pairs produce correct results
- Model is bit-accurate: all arithmetic uses fixed-width integer types (uint8_t, uint32_t, etc.)
- No floating-point arithmetic unless the spec explicitly requires it
- Test vectors cover: nominal operation, boundary conditions, overflow cases
- Generated vectors are saved to refc/vectors/ in JSON or CSV format
- Model interface matches the io_definition.json port list exactly
- All fixed-point or integer arithmetic matches the RTL bit-growth rules in the spec
- External memory access uses ext_mem_read/ext_mem_write abstraction
- bandwidth_report.json generated with external memory access statistics
</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.
- today First seen · 305 lines · 21 tokens per session scan D 90bd1c29e206
ref-model-dev is an agent published in the GitHub repository babyworm/rtl-agent-team (50 stars, last pushed 10d ago), licensed MIT. It adds 21 tokens to every session and 3,878 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it D with 2 findings (strips warnings and disclaimers, recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other agents, from other repositories
windows-engineer
Windows API, Win32 programming, IOCTL driver communication, ConPTY terminal, DPAPI encryption, DWM composition, window management, system calls, PE format, Windows internals for AiDA.
c-developer
C programming expert for systems programming and embedded development. Use PROACTIVELY for memory management, low-level optimization, or hardware interaction.
PortCSharpToCpp
Use when: analyzing C# source code to understand intent, mapping C# patterns to C++ idioms, identifying what to port vs. redesign, documenting behavioral contracts from C# implementation, gap analysis between C# and C++ SDKs, contract types inventory.
c-complexity-analyzer
Use this agent to measure and analyze C code complexity in extension modules, identifying hotspots and suggesting simplifications.\n\n \nUser: What are the most complex functions in this extension?\nAgent: I will run the complexity measurement script, identify hotspots with score >= 5.0, assess inherent vs reducible…
light-review-step1
Stage 1 of the Delphi review pipeline — a thorough, critical code review of Delphi source files. This is NOT a style checker — it reads code to understand intent, then verifies correctness. Use it for our own project code when you need a real review. Do NOT use it for 3rd-party imports (use light-code-StyleChecker for…
audio-architect
Technical architect specialising in audio software systems — designs and reviews architectures spanning C, WASM, and multi-platform targets (Linux, macOS, Windows), with deep knowledge of Pure Data, Faust, CSound, and JUCE including the engine/UI boundary in each.