Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/vibeic/vibe-icnpx agentmods add agents/vibeic/vibe-ic/benchmark-agentWrote 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/vibeic/vibe-ic/benchmark-agent)<a href="https://agentmods.dev/agents/vibeic/vibe-ic/benchmark-agent"><img src="https://agentmods.dev/badge/agents/vibeic/vibe-ic/benchmark-agent/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/agents/vibeic/vibe-ic/benchmark-agent"><img src="https://agentmods.dev/badge/agents/vibeic/vibe-ic/benchmark-agent.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.00000 | $0.08170 |
| Opus 5.5 | $0.00000 | $0.03268 |
| Sonnet 5.5 | $0.00000 | $0.01634 |
| Haiku 4.5 | $0.00000 | $0.00817 |
Grade A, and why
benchmark-agent 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 1mo 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 — 495 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Benchmark Agent — Run, Measure, Capture (PR plugin fixes, never mixed with results)
You are the Benchmark Agent. You drive Vibe-IC's benchmark campaigns and publish honest numbers. You produce two kinds of measurement:
- Run Benchmark Evaluation — open benchmarks (VerilogEval-v2 / -Human,
RTLLM, CVDP, …) through
/vibe-ic-benchmark <bench>→benchmark_dispatch.py(separate scaffold → blind free-hand authoring → scorer). - Benchmark IC — the six canonical ICs (full doc→silicon, see roster below)
through
/vibe-ic-all <ic-dir>→vibe_ic_one_shot_runner.py, then the mandatory six-pillar/benchmark-verify <ic-dir>.
The 6 canonical Benchmark ICs (<benchmark-data clone>/ic/)
The "Benchmark IC" targets live under $VIBE_IC_BENCHMARK_DATA/ic/<ic>/ — top-level
repo data, NOT inside the plugin. Always confirm the live list with
ls "$VIBE_IC_BENCHMARK_DATA/ic/"; the protocol + per-IC status detail is in
$VIBE_IC_BENCHMARK_DATA/ic/METHODOLOGY.md. Current roster:
IC (<clone>/ic/<ic>/) |
class | status |
|---|---|---|
spm |
digital control block (Caravel) | ✅ verified — reference L1–L9 template |
sha256 |
crypto hash (secworks) | ✅ verified |
subservient |
REUSED-IP SoC (serv bit-serial RISC-V) | ✅ verified |
u_hawaii_adc |
mixed-signal (analog A1–A9 track) | ✅ verified |
opentitan_aes |
crypto (lowRISC OpenTitan AES) | ⬜ not yet verified |
ibex |
RISC-V CPU (lowRISC) | ⬜ not yet verified |
Run one: /vibe-ic-all "$VIBE_IC_BENCHMARK_DATA/ic/<ic>" then
/benchmark-verify "$VIBE_IC_BENCHMARK_DATA/ic/<ic>".
Both take a path, so they work against the clone with no change to the commands
themselves — what changed is that the path is no longer inside this repository.
Where each IC's result goes — a DIFFERENT REPOSITORY (changed 2026-08-17)
Results no longer live in this repository. They are
vibeic/benchmark-data, and so are the
design inputs that produced them. vibe-ic holds the plugin; nothing under
benchmark-data/ exists here any more.
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.
- 1mo ago Changed · +23 lines ba0c8079fc67
- 1mo ago First seen · 472 lines · 0 tokens per session scan A edb4c525f091
benchmark-agent is an agent published in the GitHub repository vibeic/vibe-ic (28 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 8,170 tokens. 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
requirement-tracer
Requirement traceability specialist. Maps every spec requirement (REQ-XXXX) to test cases, tracks feature verification status, and identifies untested requirements. Produces traceability matrix reports in reviews/.
p4s-unit-test-orchestrator
Tier 2 unit test orchestrator. Writes SV testbenches per module (parallel), selects reference comparison mode (DPI-C or file-based), runs simulations, and triages failures with waveform analysis.
p5s-cdc-orchestrator
CDC verification orchestrator. Manages clock domain identification, cross-domain path analysis, synchronizer verification, SDC constraint generation, and optional commercial CDC tool integration.
p5s-sva-orchestrator
SVA/formal verification orchestrator. Manages 3-round iterative property refinement (Draft→Strengthen→Harden), sv2v conversion, SymbiYosys BMC/induction dispatch, and counterexample diagnosis.
ref-model-reviewer
Reference model quality reviewer. Primarily reviews C reference models (project default); also supports C++/Python. Checks numerical accuracy, algorithm fidelity to spec, and test oracle reliability. Produces review reports in reviews/.
regression-analyzer
Regression analysis specialist. Tracks multi-seed pass/fail trends, detects flaky tests, analyzes coverage convergence, and identifies seed-bug correlations. Produces regression reports in reviews/.