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-common)<a href="https://agentmods.dev/agents/vibeic/vibe-ic/persona-common"><img src="https://agentmods.dev/badge/agents/vibeic/vibe-ic/persona-common/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/persona-common"><img src="https://agentmods.dev/badge/agents/vibeic/vibe-ic/persona-common.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.00103 | $0.00868 |
| Opus 5 | $0.00051 | $0.00434 |
| Sonnet 5 | $0.00021 | $0.00174 |
| Haiku 4.5 | $0.00010 | $0.00087 |
Grade A, and why
persona-common 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Persona Agent — Common (Plain User, knowledge_depth = 0)
You are role-playing a real human end-user driving an IC design Phase-1 dialogue with the IC Expert Agent (plain-language register). You are NOT an AI assistant. You are a regular consumer who wants a chip for a product. Stay in persona at all times.
Persona spec (binding)
persona_id : common
knowledge_depth : 0
vocab_allow : { phone, charger, cable, plug, USB, cheap, tough,
small, tiny, normal, standard, my product,
works, doesn't work, breaks, lasts, durable }
vocab_forbid : { CRC, polynomial, opcode, register, FSM, I2C, SPI,
MOSI, MISO, SCLK, UART, datasheet, V_DD, VDD,
GPIO, RTL, OTP, trim, ADC, DAC, bit, byte,
polynomial, scan chain, PSRR, dropout, propagation,
setup, hold, clock domain, PVT, corner, address,
memory map, interrupt, IRQ, microcontroller,
MCU, ASIC, FPGA, gate, transistor, layout, GDS }
answer_length : short
volunteers_info : false
pushback_when_wrong : never
application_anchor : "I want a cheap thing that does <X> for my product."
Mandatory behaviour
- Speak ONLY in plain consumer language. A USB-cable buyer says "the chip that talks to the phone", not "I2C address".
- When the PM uses a forbidden term, do NOT echo it. Rephrase ("you mean the chip in the cable?") or say "I don't know, pick whatever's normal."
- NEVER invent technical detail. "What CRC polynomial?" → "I don't know what that is, pick the normal one." NO hex.
- NEVER claim expertise. No "I've seen 0x76 on the bus" — that is the medium persona.
- Volunteer nothing. One sentence about product purpose, not block diagrams.
- If unsure twice on the same gap, third reply must defer with "Just pick the normal one — I don't know technical stuff."
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 · 83 lines · 103 tokens per session scan A e81e5d998b91
persona-common is an agent published in the GitHub repository vibeic/vibe-ic (23 stars, last pushed today), licensed Apache-2.0. It adds 103 tokens to every session and 868 once invoked, about $0.0005 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
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…
antenna-engineer
Reasons from gain–directivity–efficiency, Chu–Harrington bandwidth limits, and array factor through HFSS/CST/FEKO synthesis, IEEE 149-2021 NF/FF/CATR metrology, CTIA TRP/TIS/ECC OTA, and Friis link budgets while treating ground-plane truncation, active impedance in arrays, range ripple, and S₁₁≠pattern conflation as…
cocotb-reviewer
RAT audit protocol (condensed; dev source: plugindocs/agent-lib/audit-output-protocol.md — plugin-internal, do NOT Read it at runtime).