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 physical-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/physical-verification)<a href="https://agentmods.dev/skills/hdl-tools/analog-chip-design-agents/physical-verification"><img src="https://agentmods.dev/badge/skills/hdl-tools/analog-chip-design-agents/physical-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/physical-verification"><img src="https://agentmods.dev/badge/skills/hdl-tools/analog-chip-design-agents/physical-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.00077 | $0.02045 |
| Opus 5 | $0.00039 | $0.01022 |
| Sonnet 5 | $0.00015 | $0.00409 |
| Haiku 4.5 | $0.00008 | $0.00204 |
Grade A, and why
physical-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 — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Physical Verification
Invocation
- If invoked by a user presenting a physical-verification task: immediately spawn the
analog-chip-design-agents:physical-verification-orchestratoragent and pass the full user request and any available context. Do not execute stages directly. - If invoked by the
physical-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/physical-verification/knowledge.md— known DRC waiver patterns, LVS debug recipes, antenna fixes, PDK deck quirks. Incorporate its guidance into every check.memory/physical-verification/run_state.md— current run identity for resume-after-interruption.
Purpose
Verify a custom layout against the foundry rule deck and the source netlist: DRC, LVS,
antenna/ERC, and density/DFM, ending in a physically-clean sign-off. Five stages with explicit
QoR gates. On a DRC or LVS failure the layout cannot self-resolve, this domain opens a
fix_request routed by the pipeline-orchestrator to custom-layout.
Supported EDA Tools
Open-Source
- Magic (
magic) — DRC and device extraction for LVS - Netgen (
netgen) — LVS (layout-vs-schematic netlist comparison) - KLayout (
klayout) — DRC / LVS decks (sky130/gf180mcu/ihp-sg13g2; predictive freepdk45/asap7, the latter with multi-patterning/coloring rules), antenna checks
Proprietary (detect-only — never installed)
- Siemens Calibre nmDRC / nmLVS (
calibre) — industry DRC/LVS sign-off - Synopsys IC Validator (ICV) (
icv) - Cadence Pegasus / Assura (
pegasus) - Silvaco Guardian — DRC/LVS/ERC
Stage: drc
Domain Rules
- Run the foundry DRC deck (Magic + KLayout) for the target
constraints.pdk; resolve every violation to 0 unwaived. - Fix spacing/width/enclosure now; defer density/antenna-adjacent rules to their dedicated stages.
- Document any intentional waiver with a foundry-acceptable justification; an undocumented waiver is a failure.
- A DRC failure the layout cannot self-resolve opens a
fix_requestto custom-layout (failure_class: drc_lvs).
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 · 215 lines · 77 tokens per session scan A 92ea1f394ac5
physical-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 77 tokens to every session and 2,045 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
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
jetson-diagnostic
Read-only Jetson health snapshot for identity, memory, GPU, thermal, power, storage, services, and top processes.
doca-socket-relay
Use this skill when the operator is driving the DOCA Socket Relay to bridge a socket-oriented host application onto a BlueField DPU peer without rewriting it — picking the deployment shape (in-process, sidecar, or BlueField service container), configuring the host-side socket and the DPU-side forwarding endpoint…
offensive-z-wave
Z-Wave attack methodology — sniffing with Z-Force / EZ-Wave / RTL-SDR + ZniffMobile, S0 (legacy) network-key derivation flaw and key reuse, S2 (modern) ECDH commissioning analysis, replay/injection on unauthenticated nodes, default-key brute-force on test deployments, and home-automation hub pivots. Use when targeting…
hsb-flash
Flash the FPGA on an HSB board connected to an NVIDIA devkit. Supports HSB Lattice boards (FPGA versions 2407, 2412, 2507, 2510) and Leopard Imaging VB1940 "all-in-one" cameras (FPGA versions 2507, 2510). Uses release-specific YAML manifests and board-type-specific program commands. Lattice and VB1940 commands must…
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.