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 skills/vibeic/vibe-ic/loop2convergeWrote 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/vibeic/vibe-ic/loop2converge)<a href="https://agentmods.dev/skills/vibeic/vibe-ic/loop2converge"><img src="https://agentmods.dev/badge/skills/vibeic/vibe-ic/loop2converge/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/skills/vibeic/vibe-ic/loop2converge"><img src="https://agentmods.dev/badge/skills/vibeic/vibe-ic/loop2converge.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 43 Docker image references without a specific tag (:latest is implicit) or digest (@sha256:...) can be silently replaced by a malicious image.Fix: Pin the image: image:tag or image@sha256:abc123
- medium Rogue Agent · line 87 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Rogue Agent · line 87 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Rogue Agent · line 112 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00237 | $0.04518 |
| Opus 5.5 | $0.00095 | $0.01807 |
| Sonnet 5.5 | $0.00047 | $0.00904 |
| Haiku 4.5 | $0.00024 | $0.00452 |
Grade A, and why
loop2converge 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 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.
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 — 329 lines — stays where its author put it; the contents beside it link to each section on GitHub.
loop2converge — run, classify, converge, prove, capture, re-run
The loop exists because a benchmark number that nobody converged is a number nobody learns from, and a fix that never leaves a cache is a fix that dies with the session.
┌─ 1 RUN ─────► 2 CLASSIFY ─────► 3 CONVERGE ─────► 4 PROVE ─────► 5 CAPTURE ─┐
│ canonical flow / gate fix the layer in the CACHE PR to the │
│ front door / tool that OWNS it first owning repo│
└──────────────────────── 6 RE-RUN, and repeat until the target ───────────────┘
The loop is CLOSED: step 6 re-enters step 1 on the upgraded plugin. It terminates on the subject's own target, never on "we ran out of findings".
1 — RUN, through the ONE front door
1.0 — Bind the runtime version and preserve valid checkpoints
Before a new invocation, identify the actual plugin source and EDA image. Adopt published fixes relevant to the failure and verify the runtime binding. A version change alone does not invalidate previously accepted checkpoints or authorize a broader rerun. Keep each retained result attributed to the version that produced it.
/plugin update vibe-ic # plugin: pull the newest marketplace version
docker pull <vibeic-eda image> # tool: pull the newest fork image
# then, and this is the part that is skipped:
eda_doctor # ask the SERVER what it is serving
An install is not a binding. MEASURED 2026-08-29: the plugin was upgraded to
1.12.51 and eda_doctor still reported plugin_programs_dir: …/1.11.94/programs. An
MCP server keeps serving the version it BOOTED with; nothing about plugin update
reaches an already-running server. Every finding produced in that window described
1.11.94 while the report said 1.12.51.
So the upgrade is not complete until you have READ BACK, from the running server, that it is serving the version you installed:
| what to read back | says what |
|---|---|
eda_doctor → plugin_programs_dir |
which plugin version the MCP will actually execute |
eda_doctor → the EDA image digest/label |
which fork build the tools come from |
| the plugin's own version in the run's report | what the flow believes it is |
What ships with it
2 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.
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 Changed · +19 lines 546c5f67f279
- 3d ago Changed · +36 lines 418d3d028405
- 1mo ago First seen · 274 lines · 237 tokens per session scan A 5b50f0b2c227
loop2converge is a skill published in the GitHub repository vibeic/vibe-ic (28 stars, last pushed today), licensed Apache-2.0. It adds 237 tokens to every session and 4,518 once invoked, about $0.0009 per session on Opus 5.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 skills, from other repositories
analog-verify
Pre-simulation review and Spectre simulation verification for analog circuits. Reviews circuit netlist and testbench, runs simulation, produces margin report. Use after analog-design completes a netlist.
pcb-lint
Run a battery of PCB design-hygiene checks against the board open in EasyEDA Pro, through the easyeda MCP tools, and produce a scored report. Use when the user says "/pcb-lint", "lint the board", "run PCB checks", "check my layout", "is this board ready to fab?", or finishes a PCB layout iteration and is about to…
boardrepo
Read and review real PCB projects on BoardRepo. Search published hardware designs, open a board's schematic connectivity, bill of materials and files, run KiCad's DRC and ERC, and check a design against a fabrication house's limits. Use whenever the user names a BoardRepo board or URL, asks to find a published board…
analog-netlist-crawl
Crawl and analyze post-layout parasitic netlists without running SPICE. Answers "what's the effective resistance from node A to node B across this massive R mesh?", "inside the VREFN mesh, which device pins are electrically farthest apart?", "which nets have the worst coupling?", "where does settling bottleneck?" — by…
analog-design
Transistor-level circuit design for one analog sub-block. Produces Spectre netlist with hand-calculation rationale. Use when designing a specific circuit block after architecture is defined.
analog-pipeline
MANDATORY — MUST load this skill when the user mentions: OTA, ADC, PLL, comparator, bandgap, LDO, amplifier, opamp, or any analog/mixed-signal IC design task. Full analog design pipeline: spec -> architecture -> design -> verify -> deliver. Orchestrates analog-decompose, analog-behavioral, analog-design…