parasitic-extraction

parasitic-extraction is a skill for Claude Code from hdl-tools/analog-chip-design-agents. It costs 66 tokens per session (1,989 once invoked), scanned A, original, MIT.

A layout-analysis workflow that calculates unwanted resistance and capacitance, including coupling between nearby wires. It adds those effects back into a netlist, the circuit description used for simulation.

In plain words
What is it for?
Use it to extract parasitics from a clean chip layout, create a post-layout simulation netlist, and identify layouts that need parasitic reduction.
Why use it?
It shows how the physical layout changes circuit behavior before final sign-off simulation.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the analog-design-extraction plugin — 1 skill, 1 agent shipped together

Good fit Use it to extract parasitics from a clean chip layout, create a post-layout simulation netlist, and identify layouts that need parasitic reduction.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/hdl-tools/analog-chip-design-agents/parasitic-extraction
Install

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.

Any agent
npx skills add hdl-tools/analog-chip-design-agents --skill parasitic-extraction
Clone the repo
git clone --depth 1 https://github.com/hdl-tools/analog-chip-design-agents

Made for: Claude Code.

Or install analog-design-extraction, the plugin that ships this one along with the rest of its 1 skill, 1 agent.

Wrote 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.

agentmods badge for parasitic-extraction

README.md
[![agentmods](https://agentmods.dev/badge/skills/hdl-tools/analog-chip-design-agents/parasitic-extraction/github.svg)](https://agentmods.dev/skills/hdl-tools/analog-chip-design-agents/parasitic-extraction)
Your own site
<a href="https://agentmods.dev/skills/hdl-tools/analog-chip-design-agents/parasitic-extraction"><img src="https://agentmods.dev/badge/skills/hdl-tools/analog-chip-design-agents/parasitic-extraction/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.

agentmods 80×15 button for parasitic-extraction

Your own site · 80×15
<a href="https://agentmods.dev/skills/hdl-tools/analog-chip-design-agents/parasitic-extraction"><img src="https://agentmods.dev/badge/skills/hdl-tools/analog-chip-design-agents/parasitic-extraction.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 66 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,989 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00066 $0.01989
Opus 5 $0.00033 $0.00994
Sonnet 5 $0.00013 $0.00398
Haiku 4.5 $0.00007 $0.00199

Measured 12d ago against content hash 6712ee463460, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

parasitic-extraction 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 12d 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.

plugins/extraction/skills/parasitic-extraction/SKILL.md · 212 lines

How it starts

The opening of the file, as written. The whole thing — 212 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Skill: Parasitic Extraction

Invocation

  • If invoked by a user presenting an extraction task: immediately spawn the analog-chip-design-agents:parasitic-extraction-orchestrator agent and pass the full user request and any available context. Do not execute stages directly.
  • If invoked by the parasitic-extraction-orchestrator mid-flow: 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:

  1. memory/extraction/knowledge.md — known extraction-deck settings, coupling-net recipes, back-annotation pitfalls, PDK extraction quirks. Incorporate its guidance into every run.
  2. memory/extraction/run_state.md — current run identity for resume-after-interruption.

Purpose

Extract R, C, and coupling parasitics from a physically-clean layout and build a back-annotated post-layout netlist for sign-off simulation. Five stages with explicit QoR gates. Extraction is the bridge between a clean GDS and post-layout sign-off; it gates on the pex_signoff checkpoint and flags layouts for parasitic reduction when degradation is large.


Supported EDA Tools

Open-Source

  • Magic (magic) — ext / ext2spice RC extraction
  • KLayout (klayout) — PEX (R + limited C) decks
  • FastCap / FastHenry (fastcap, fasthenry) — field-solver capacitance/inductance for critical nets

Proprietary (detect-only — never installed)

  • Synopsys StarRC (starrc) — sign-off RC extraction
  • Cadence Quantus QRC (quantus)
  • Siemens Calibre xRC / xACT (calibre)
  • Silvaco Clever — 3-D field-solver extraction

Stage: extraction_setup

Domain Rules

  1. Configure the extraction deck for the target constraints.pdk and the required extraction type (R-only, RC, or RC+coupling) based on the block's sensitivity.
  2. Define the corner (best/worst-case parasitic) and the nets requiring coupling extraction (high-Z, matched, clock).
  3. Confirm the input GDS passed physical-verification (design_state.physical_verification.signoff) before extracting.

Read the full file on GitHub · 212 lines

Changes

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.

  1. 12d ago First seen · 212 lines · 66 tokens per session scan A 6712ee463460

Subscribe to this mod's changes

parasitic-extraction is a skill published in the GitHub repository hdl-tools/analog-chip-design-agents (22 stars, last pushed 3mo ago), licensed MIT. It adds 66 tokens to every session and 1,989 once invoked, about $0.0003 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.

Related

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…

google/skills · 83 tokens

jetson-diagnostic

Read-only Jetson health snapshot for identity, memory, GPU, thermal, power, storage, services, and top processes.

NVIDIA/skills · 30 tokens

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…

NVIDIA/skills · 236 tokens

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…

SnailSploit/Claude-Red · 113 tokens

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…

NVIDIA/skills · 94 tokens

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.

NVIDIA/skills · 50 tokens