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 skills add hdl-tools/analog-chip-design-agents --skill ams-verificationgit clone --depth 1 https://github.com/hdl-tools/analog-chip-design-agentsWrote 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/hdl-tools/analog-chip-design-agents/ams-verification)<a href="https://agentmods.dev/skills/hdl-tools/analog-chip-design-agents/ams-verification"><img src="https://agentmods.dev/badge/skills/hdl-tools/analog-chip-design-agents/ams-verification/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/hdl-tools/analog-chip-design-agents/ams-verification"><img src="https://agentmods.dev/badge/skills/hdl-tools/analog-chip-design-agents/ams-verification.svg" alt="Reviewed on agentmods" width="80" 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.00075 | $0.02765 |
| Opus 5 | $0.00037 | $0.01383 |
| Sonnet 5 | $0.00015 | $0.00553 |
| Haiku 4.5 | $0.00007 | $0.00277 |
Grade A, and why
ams-verification 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 11d 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 — 251 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: AMS Verification
Invocation
- If invoked by a user presenting a mixed-signal verification task: immediately spawn the
analog-chip-design-agents:ams-verification-orchestratoragent and pass the full user request and any available context. Do not execute stages directly. - If invoked by the
ams-verification-orchestratormid-flow (including re-validation): do not spawn a new agent. Treat this file as read-only — return the requested stage rules, sign-off criteria, or loop-back guidance.
Spawning the orchestrator from within an active orchestrator run causes recursive delegation and must never happen.
Pre-run Context
Before executing or advising on any stage, read the following if they exist:
memory/ams-verification/knowledge.md— known co-sim sync pitfalls, connect-rule recipes, RNM-vs-SPICE divergence patterns, coverage-closure tactics. Incorporate its guidance.memory/ams-verification/run_state.md— current run identity for resume-after-interruption.
Purpose
Verify an analog/mixed-signal block against its digital control: build mixed-signal
testbenches, define connect rules, run analog-digital co-simulation and real-number-model
regressions, and close functional coverage. Six stages with explicit QoR gates. On a
mismatch the testbench cannot resolve, this domain opens a fix_request routed by the
pipeline-orchestrator to behavioral-modeling (model fault) or circuit-design (circuit fault).
Supported EDA Tools
Open-Source
- cocotb (
python -m cocotb) + ngspice / Xyce — analog-digital co-simulation harness - Verilator (
verilator) / Icarus (iverilog) — digital + RNM regression - Xyce (
Xyce) — mixed-signal SPICE for the analog side
Proprietary (detect-only — never installed)
- Cadence Xcelium AMS / AMS Designer (
xrun) — AMS co-sim + coverage - Spectre AMS (
spectre) — analog engine for AMS - Synopsys VCS-AMS / CustomSim (
vcs) — AMS co-sim - Siemens Symphony + QuestaSim — AMS + digital co-sim
- AFS-driven co-sim (
afs) — fast-SPICE analog engine
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.
- 11d ago First seen · 251 lines · 75 tokens per session scan A b0acecd75e08
ams-verification is a skill published in the GitHub repository hdl-tools/analog-chip-design-agents (22 stars, last pushed 3mo ago), licensed MIT. It adds 75 tokens to every session and 2,765 once invoked, about $0.0004 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
jetson-video-pipeline
Use when executing and verifying Jetson Video Codec SDK or PyNvVideoCodec encode/decode, transcode, segmentation, container decode, AV1, or acceptance workflows with exact artifact handoffs.
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
holohub-app-lifecycle
Use for non-failing HoloHub app work with ./holohub: scaffold, build, run, test, visual evidence, lint, and flow benchmarking.
code-plan
Turn a task description and repository into a structured implementation plan (files to create, files to modify, tests to add, risks).
ros2-robotics
Best practices for ROS 2 robotics development, covering package structure, nodes, topics/services/actions, launch files, QoS, tf2 transforms, and testing. Use when creating ROS 2 packages, writing nodes in rclpy or rclcpp, defining custom messages/services/actions, writing launch files, configuring QoS profiles…
SmartHome Video Anomaly Benchmark
VLM evaluation suite for video anomaly detection in smart home camera footage.