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/lvs-triageWrote 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/lvs-triage)<a href="https://agentmods.dev/skills/vibeic/vibe-ic/lvs-triage"><img src="https://agentmods.dev/badge/skills/vibeic/vibe-ic/lvs-triage/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/lvs-triage"><img src="https://agentmods.dev/badge/skills/vibeic/vibe-ic/lvs-triage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00068 | $0.03334 |
| Opus 5.5 | $0.00027 | $0.01334 |
| Sonnet 5.5 | $0.00014 | $0.00667 |
| Haiku 4.5 | $0.00007 | $0.00333 |
Grade A, and why
lvs-triage 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 1mo 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 — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LVS Triage
LVS proves that the drawn layout corresponds to the schematic / netlist. Mismatches are common in early iterations. This skill reads LVS reports (Calibre, Netgen, Pegasus) and proposes focused fixes.
When to use
- After routing / layout finalization
- After any manual layout edit
- Before tapeout sign-off
- When integrating analog macros into a digital floorplan
Inputs
- LVS report file (Calibre
.rep, Netgencomp.out, etc.) - Schematic netlist (
.cdl/.sp/.v) - Extracted layout netlist
- Device model list (PDK-specific)
Workflow
- Parse report into categories:
- Unmatched instances
- Unmatched nets (shorts, opens)
- Device parameter mismatches (W/L, M, NF)
- Property mismatches (labels, dummies)
- Top-3 root-cause check:
- Missing label on a net (most common)
- Missing via between metal layers
- Wrong device variant picked from PDK
- For each mismatch propose the exact layer + coordinate to edit
- Batch waivers: some analog dummies intentionally don't appear in schematic — document waiver
- Re-run plan: minimal LVS subset to re-verify
Output format
lvs/lvs_triage.md:- Mismatch summary (count by category)
- Top 20 mismatches with fix
- Waiver list with justification
- Re-run script
Technical basis
LVS methodology references: Mentor Calibre user guide, open-source Netgen (http://opencircuitdesign.com/netgen/). Signoff tools: Calibre LVS, Cadence Pegasus, Synopsys IC Validator.
Structural-LEC "unproven cells" are a substitute-tool gap — cover with device-level LVS (captured v0.1.98)
eda_lvs mode=yosys_equiv is structural LEC (yosys equiv_simple+equiv_induct): it proves
Boolean equivalence with a SAT engine. That engine lacks a model for some standard-cell
primitives, so those cells come back "unproven" / sat_model_unsupported_cells — this is a
LIMITATION OF THE SUBSTITUTE TOOL, not a netlist mismatch, and no yosys flag closes it for
all cells (-undef, deeper equiv_induct -seq N, dfflibmap/async2sync only widen it).
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.
- 1mo ago First seen · 222 lines · 68 tokens per session scan A 150923a6cbb0
lvs-triage is a skill published in the GitHub repository vibeic/vibe-ic (28 stars, last pushed today), licensed Apache-2.0. It adds 68 tokens to every session and 3,334 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
vivado-cdc-audit
A Vivado workflow for reviewing clock-domain crossing, or CDC, reports in FPGA designs. CDC checks whether signals moving between unrelated clock rates are synchronized and transferred safely.
vivado-timing-closure
A Vivado workflow for finding and fixing setup, hold, and pulse-width timing problems in FPGA designs. Timing closure means meeting the required signal timing without changing the design's intended behavior.
vivado-waveform-debug
A Vivado waveform-debugging workflow for examining VCD simulation traces, which record signal values over time. It can query selected signals and time ranges without opening a full Vivado session.
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-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.