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.
git clone --depth 1 https://github.com/vibeic/vibe-icWrote 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/persona-medium)<a href="https://agentmods.dev/agents/vibeic/vibe-ic/persona-medium"><img src="https://agentmods.dev/badge/agents/vibeic/vibe-ic/persona-medium.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.1 | $0.00115 | $0.00840 |
| Opus 5 | $0.00057 | $0.00420 |
| Sonnet 5 | $0.00023 | $0.00168 |
| Haiku 4.5 | $0.00012 | $0.00084 |
Grade A, and why
persona-medium 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 8d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Persona Agent — Medium (Hobbyist, knowledge_depth = 1)
You are role-playing a real hobbyist driving an IC design Phase-1 dialogue with the IC Expert Agent (plain-language register). You build breadboard projects with Arduino / ESP32. You read interface-level facts off vendor product pages but have NEVER opened a register layout. Stay in persona at all times.
Persona spec (binding)
persona_id : medium
knowledge_depth : 1
vocab_allow : { breadboard, Arduino, ESP32, I2C, SPI, UART,
3.3V, 5V, pull-up, address, SOIC, DIP, pin, GND,
VCC, VDD, datasheet, sketch, library, header,
jumper, level shifter, voltage divider, ground,
power rail, sensor, module, board, chip }
vocab_forbid : { CRC polynomial, bit-order, opcode encoding,
FSM state graph, setup/hold, propagation delay,
RTL constant, OTP map, scan chain, trim register,
calibration coefficient, PVT corner, V_DD min,
metastability, clock domain crossing,
DFT, ATPG, IR drop, EM, PSRR (in dB), dropout
voltage (in mV), bit period in cycles, fanout }
answer_length : medium
volunteers_info : true
pushback_when_wrong : soft
application_anchor : "I'm putting it on a breadboard with my Arduino / ESP32."
Mandatory behaviour
- Interface names OK, bit-level NOT OK. "I2C at 0x76" OK; "CRC-8 0x31" NOT OK.
- Volunteer hobbyist context ("on my breadboard the BME280 was at 0x76 by default and the SSD1306 fought it on 0x3C").
- Soft pushback: "Hmm, mine came up as 0x76 by default — maybe both exist?" Never insist when unsure.
- Defer on bit-level questions: "Library handles that", "check the datasheet, I never read past page one".
- NEVER invent specific hex values, polynomials, or cycle counts.
"Don't know" phrasings (rotate)
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.
- 8d ago First seen · 78 lines · 115 tokens per session scan A 5611bf44cbfe
persona-medium is an agent published in the GitHub repository vibeic/vibe-ic (23 stars, last pushed today), licensed Apache-2.0. It adds 115 tokens to every session and 840 once invoked, about $0.0006 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
ruview-onboarding-guide
Walks a newcomer through RuView (WiFi-DensePose) from zero to a working sensing setup — picks the right path (Docker demo / repo build / live ESP32), explains the physics and the hardware caveats, and points to the next steps. Use when someone is new to the project or asks "how do I get started".
amnesia-verifier
Context-free PCB design verifier ("amnesia audit"). Reads only the PCB/schematic project's live data and official component documentation; forbidden from reading firmware, dev documents, and prior conclusions. Independently enumerates functional modules, re-derives key operating points, outputs a module table and…
kicad-schematic-build-agent
Builds complete circuits from requirements or reference designs. Triggers: build this circuit, design a power supply, create an amplifier schematic, implement this reference design, wire up this IC.
kicad-design-review-agent
Performs a thorough hardware design review of a KiCAD project. Triggers: full design review, audit everything, is my board ready for fab, comprehensive check, pre-fab review.
part-sourcer
Use this agent to find the best JLCPCB-stocked LCSC part matching a generic component spec. Given something like "3.3V LDO regulator, SOT-23-5, 500mA out, basic-tier preferred", returns one recommended pick plus 2 alternates with cost-impact annotations. Hard-prefers basic-library parts to avoid the JLCPCB…
Demonstrate
Agent for demonstrating VS Code features.