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/ams-simWrote 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/ams-sim)<a href="https://agentmods.dev/skills/vibeic/vibe-ic/ams-sim"><img src="https://agentmods.dev/badge/skills/vibeic/vibe-ic/ams-sim/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/ams-sim"><img src="https://agentmods.dev/badge/skills/vibeic/vibe-ic/ams-sim.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.00105 | $0.01292 |
| Opus 5 | $0.00053 | $0.00646 |
| Sonnet 5 | $0.00021 | $0.00258 |
| Haiku 4.5 | $0.00011 | $0.00129 |
Grade A, and why
ams-sim 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 9d 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AMS Sim
Analog blocks must be verified across process corners, temperature, voltage, and mismatch. This skill plans the testbench matrix, generates the simulator decks, and triages results.
When to use
- After
/analog-sizingproduces a schematic - After
/analog-layout+ extraction (post-layout) - When mismatching is the suspected failure mode (Monte Carlo)
- Mixed-signal co-simulation with a digital controller (ngspice + Verilog-A, or Spectre APS)
Inputs
- Schematic / netlist (
.sp,.cir,.scs) - Device models from PDK (
.lib/.scs) - Specs to verify (gain, BW, PSRR, CMRR, noise, slew, settling, offset)
- Corner definition (FF/SS/TT/FS/SF × temp × supply)
- Monte Carlo N (typical 500–5000 runs)
Analysis matrix
| Analysis | Purpose |
|---|---|
.op |
DC operating point, bias validation |
.dc |
Sweeps (supply, input, parameter) |
.ac |
Gain, bandwidth, phase margin |
.tran |
Settling, slew, large-signal |
.noise |
Input-referred noise, SNR |
.pss / .pac / .pnoise |
Periodic steady-state (for RF / SC circuits) |
.mc |
Monte Carlo mismatch + process |
The spec → required-analysis-subset mapping in this table is a frozen
lookup, enforced by programs/ams_analysis_select.py — do NOT pick
the analysis set by hand (two agents would otherwise pick different /
incomplete subsets for the same spec list). Run it on the block's
spec.json (or the project dir to scan analog/*/spec.json) and use
the emitted analyses set:
python3 programs/ams_analysis_select.py <block>/spec.json
# -> {"analyses": [".op", ".ac", ".tran", ".noise"], "mapping": [...]}
It always selects .op (bias validation) when ≥1 measurable spec is
present, adds .mc whenever any spec declares a mismatch / σ / yield
concern, and FAILs honestly (exit 1) when a spec carries no recognizable
measurable metric. Agent judgment is only needed to override an
ambiguous / custom spec key the table does not recognize.
Workflow
- Pick the analysis subset — enforced by
programs/ams_analysis_select.py(see Analysis matrix) - Build deck with corner + MC sweeps
- Run (ngspice / Xyce / Spectre / HSPICE)
- Extract measurements via
.measstatements — generated byprograms/analog_meas_from_spec_gen.py - Tabulate corners × MC yield vs spec — enforced by
programs/corner_yield_vs_spec_check.py(re-derives per-corner / per-spec PASS/FAIL fromspec.jsonmin/max limits + reports the worst, smallest-margin corner) andprograms/analog_corner_sweep_check.py(gates ≥9-corner PVT count + all-spec-pass). Do NOT hand-tabulate the yield table — quote these programs' verdicts. - Flag failing corners — the worst corner is the
worst_cornerfield fromcorner_yield_vs_spec_check.py; PVT-coverage gaps are classified byprograms/corner_coverage_audit.py. Propose sizing or layout changes (agent judgment). - Hand off to re-sizing loop
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.
- 9d ago First seen · 106 lines · 105 tokens per session scan A 50b32bb9786c
ams-sim is a skill published in the GitHub repository vibeic/vibe-ic (23 stars, last pushed today), licensed Apache-2.0. It adds 105 tokens to every session and 1,292 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 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-wiki
Knowledge graph for analog circuit design. Stores topologies, strategies, corner lessons, anti-patterns, and project cases. Query with consult, add entries, track relationships, archive project cases. Use to build and query design knowledge across projects.
adc-analyzer
ADC characterization orchestrator in the analog-agents project. Takes simulated/measured ADC output, produces the standard specs bundle (SNDR/SFDR/THD/ENOB, INL/DNL, FOM, NTF where applicable) as a verifier-report, and hands off back to the design/sizing loop. TRIGGER when the user asks to characterize an ADC, extract…
train-pose
Train/evaluate WiFi pose models honestly — camera-supervised (MediaPipe + CSI) and camera-free (WiFlow), always checked against the mean-pose baseline before any PCK is quoted.
experiment-audit
A review step that checks whether an experiment's reported results are supported by real data and a sufficiently broad test.