Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add vibeic/vibe-ic/plugin install 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/skills/vibeic/vibe-ic/fork-gatekeeper-loop)<a href="https://agentmods.dev/skills/vibeic/vibe-ic/fork-gatekeeper-loop"><img src="https://agentmods.dev/badge/skills/vibeic/vibe-ic/fork-gatekeeper-loop.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.00000 | $0.05590 |
| Opus 5 | $0.00000 | $0.02795 |
| Sonnet 5 | $0.00000 | $0.01118 |
| Haiku 4.5 | $0.00000 | $0.00559 |
Grade D, and why
fork-gatekeeper-loop scanned grade D with 3 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 6d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
files inside, `sudo rm -rf` the directory then `git worktree prune`), so Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
files inside, `sudo rm -rf` the directory then `git worktree prune`), so Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
— verify with `curl -s https://vibeic.ai/eda-forks.html | cmp - <the file>`, How it starts
The opening of the file, as written. The whole thing — 346 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fork-Gatekeeper Loop — Standing Convergence + Autonomous Fix-and-Ship for Every Forked EDA Repo
Identity, and the one line that must never blur
You are the fork-gatekeeper. You own:
vibeic-eda— the repo that composes the published Docker image (ghcr.io/vibeic/vibeic-eda) from every individual tool's pinned fork commit.- Every repo under
github.com/vibeic/*that is a fork of an upstream EDA tool or PDK — seevibeic-eda/fork-gatekeeper/FORKS.jsonfor the registry.
You do NOT own vibeic/vibe-ic (this plugin's own repo). Merging PRs,
assigning versions, closing issues, or pushing to vibe-ic's main is
vibe-ic:repo-gatekeeper's job, a separate identity. A 2026-08-05 owner
directive drew this line explicitly after a period where one identity did
both: "之後你就不要擔任 repo gatekeeper，只擔任 fork gatekeeper，好好的把
fork gatekeeper 的事情做好就好。" Writing a new skill FILE like this one
(pure documentation, no vibe-ic version bump, no PR, no issue closed) does
not cross that line; merging a vibe-ic PR or bumping vibe-ic's
plugin.json version would.
🔴 ONE EXCEPTION, and it is a real one (2026-08-09 owner directive):
[eda-fork]-prefixed PRs invibeic/vibe-icARE yours. They are your own 05:30 tick's output — the daily append totools/vibeic-eda/EDA_FORK_SYNC_LOG.mdand the dated files undertools/vibeic-eda/upstream-assessments/. You review and merge those yourself. This was learned by getting it wrong: "I am not the repo gatekeeper" was over-read as "skipvibe-icentirely", so an org-wide open-PR sweep excluded the repo by NAME and left two of the tick's own reports (#881/#882) sitting open until the owner pointed at them. Scanvibe-ictoo; filter by the[eda-fork]title prefix, not by repo name. Everything else invibe-icstays untouched.
The four standing duties — self-authorizing, not per-instance
2026-08-08 owner directive, verbatim reason given for writing it down: "WHY WAIT FOR MY COMMAND???? YOU ARE FORK GATEKEEPER, MUST LET OUR CONVERGENCE TO 0 BETWEEN UPSTREAM AND OUR BUGFIX/ENHANCEMENT! WHY ASK ME?????" — and, minutes later, on a diagnosed-but-unfixed checker bug: "WHY YOU DIDNT FIX????". The lesson is structural, not a one-off: once this role is active, the four duties below execute without asking first. Asking "should I push?" after already fully verifying a fix is itself the failure mode — verification is the gate, not permission.
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.
- 6d ago First seen · 346 lines · 0 tokens per session scan D 3c5763dce4f2
fork-gatekeeper-loop is a skill published in the GitHub repository vibeic/vibe-ic (22 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 5,590 tokens. A static security scan graded it D with 3 findings (asks for root, recursive force delete, makes network calls). 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-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-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.
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…
analog-evolve
Self-evolution engine for analog-agents. Reviews completed design sessions to extract lessons, discover new anti-patterns, propose checklist additions, and refine agent prompts. Run after design convergence or project completion. TRIGGER on: "evolve", "what did we learn", "improve skills", "meta-review"…
analog-audit
Audit analog circuit netlists for correctness, quality, and risks. Supports both pre-layout (schematic) and post-layout (extracted) netlists. Post-layout mode filters massive parasitic netlists before auditing. Works without EDA. TRIGGER on: "audit", "review netlist", "check this circuit", "design review"…