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.
npx agentmods add skills/vibeic/vibe-ic/gatekeeper-loopnpx skills add vibeic/vibe-ic --skill gatekeeper-loopgit 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/skills/vibeic/vibe-ic/gatekeeper-loop)<a href="https://agentmods.dev/skills/vibeic/vibe-ic/gatekeeper-loop"><img src="https://agentmods.dev/badge/skills/vibeic/vibe-ic/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.09344 |
| Opus 5 | $0.00000 | $0.04672 |
| Sonnet 5 | $0.00000 | $0.01869 |
| Haiku 4.5 | $0.00000 | $0.00934 |
Grade A, and why
gatekeeper-loop 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 2d 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 — 607 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Case-study notation. This skill uses
PR-A/branch-Aas the canonical example PR — substitute the real PR number and branch. The rules themselves are chip-AGNOSTIC and apply to any PR againstmain, independent of which IC / vendor / SKU the PR touches. When you adopt this skill, swapPR-A→#<your PR number>andbranch-A→<your head ref>; the structural gates and the merge-queue protocol do not depend on those values.
Gatekeeper Loop — Single-Owner PR-Merge Loop for main
Purpose
DOCTRINE NOTE (2026-06-26 owner directive — STANDING preference; supersedes the 2026-06-17 PR-method). The maintainer now ships its OWN fixes by direct push to
main(direct commit +git push origin main, NOgh pr create— seevibe-ic:core-agent-loop§Step 3). The gatekeeper's gate SEQUENCE is unchanged and still authoritative — it is just applied PRE-PUSH on the main checkout (drivegatekeeper_review.pyto MERGE_OK → Step-2.7 on any guard/transform diff →gatekeeper_assign_version.py --write→git push) instead of on a PR branch. The PR-merge-queue machinery in this skill is RETAINED for any PR filed from ELSEWHERE (an external contributor, or a legacy in-flight branch): such a PR is still gated + version-assigned + squash-merged exactly as below. Doctrine history (so the flip-flop is legible): direct-push through v1.1.5 → PR-method 2026-06-17 → direct-push again 2026-06-26; the gates are retained in every era, only the landing ceremony changed.
Two-layer framing. The maintainer's own direct-push fixes are Layer 2 (the internal improvement-phase shortcut). The PR-merge-queue machinery in this skill is Layer 1 — the public contribution model: an external contributor files a backlog (a report) or a PR (a fix), and you are the sole merger of those PRs. Both layers cross the identical gate sequence; only Layer-1 adds the PR ceremony. External contributors never push to
main.
What ships with it
3 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.
- 2d ago Changed · +6 lines f51701785f89
- 5d ago First seen · 601 lines · 0 tokens per session scan A 8c0d932d4e95
gatekeeper-loop is a skill published in the GitHub repository vibeic/vibe-ic (22 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 9,344 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 skills, from other repositories
cadence-virtuoso
Comprehensive operational skill specification for Anthropic Claude to automate, script, troubleshoot, and optimize Cadence Virtuoso, SKILL language, OCEAN simulation scripts, Spectre engine, and DRC/LVS verification.
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-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"…