automating-orcad-capture-tcl

automating-orcad-capture-tcl is a skill for Claude Code, Codex from redstone39/orcad-capture-toolkit. It costs 109 tokens per session (944 once invoked), scanned A, original, MIT.

A guide for automating OrCAD Capture, an electronic-circuit schematic design tool, with Tcl scripts. It covers schematic files, parts, wires, ports, libraries, and design databases.

In plain words
What is it for?
Use it to write or debug scripts that place schematic parts, connect wires, edit properties, inspect designs, recover libraries, or work with component databases.
Why use it?
It clarifies which OrCAD automation commands and file types apply, while avoiding unrelated PCB, simulation, and export tasks.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to write or debug scripts that place schematic parts, connect wires, edit properties, inspect designs, recover libraries, or work with component databases.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/redstone39/orcad-capture-toolkit/orcad-capture-toolkit
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 redstone39/orcad-capture-toolkit --skill orcad-capture-toolkit
Clone the repo
git clone --depth 1 https://github.com/redstone39/orcad-capture-toolkit

Made for: Claude Code, Codex.

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 automating-orcad-capture-tcl

README.md
[![agentmods](https://agentmods.dev/badge/skills/redstone39/orcad-capture-toolkit/orcad-capture-toolkit/github.svg)](https://agentmods.dev/skills/redstone39/orcad-capture-toolkit/orcad-capture-toolkit)
Your own site
<a href="https://agentmods.dev/skills/redstone39/orcad-capture-toolkit/orcad-capture-toolkit"><img src="https://agentmods.dev/badge/skills/redstone39/orcad-capture-toolkit/orcad-capture-toolkit/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 automating-orcad-capture-tcl

Your own site · 80×15
<a href="https://agentmods.dev/skills/redstone39/orcad-capture-toolkit/orcad-capture-toolkit"><img src="https://agentmods.dev/badge/skills/redstone39/orcad-capture-toolkit/orcad-capture-toolkit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 109 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 944 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.00109 $0.00944
Opus 5 $0.00055 $0.00472
Sonnet 5 $0.00022 $0.00189
Haiku 4.5 $0.00011 $0.00094

Measured 8d ago against content hash 2c8bce3c8dcf, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

automating-orcad-capture-tcl 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 8d 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.

SKILL.md · 58 lines

How it starts

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

OrCAD Capture Toolkit — Skill Entry Point

AI agents: read this file and references/ai-usage.md.

When to Trigger This Skill

Load and use this skill whenever a user request falls into any of the following scenarios:

  • Writing, modifying, or debugging any OrCAD Capture TCL script
  • Mentions of .DSN / .OLB / design cache / Capture automation
  • Placing parts / wires / ports, editing properties, or reading schematic structure with PlacePart / PlaceWire / PlacePort
  • Recovering a part from an inherited design into a standalone library
  • Probing whether the CIS Tcl surface is available, or deciding between Unified CIS / Legacy CapCIS
  • Any TCL-related question on the Cadence SPB schematic side

Out-of-Scope (Do Not Force This Skill)

  • PCB-side / Allegro-side TCL (routing, constraints, shapes, padstacks) — that is a separate API set
  • PSpice simulation — simulation commands, profile configuration, waveform analysis
  • Constraint Manager rule editing
  • Netlist export to other formats (Allegro / Verilog / Spice / EDIF)
  • Project Manager file-level operations — e.g., archive, tar/zip project
  • OrCAD X / Cloud API specifics (some surfaces may differ)
  • Skill / library-level schematic editing (inherits / sub-circuit hierarchy editing)
  • Batch merging multiple parts into one .OLB (this toolkit's design cache recovery handles only a single part)

When these topics arise, inform the user that this toolkit does not cover them and suggest they look for dedicated PCB / PSpice / Constraint Manager resources.

Workflow for AI Agents

  1. Read references/ai-usage.md — decision tree + output specification + composable idiom building blocks (primary entry point)
  2. Read the relevant references/ module — verify viable APIs, known pitfalls, and version dependencies
  3. Check references/anti-patterns.md — confirm the APIs you intend to use are not on the DO NOT list
  4. Build on the §5 idiom blocks in ai-usage.md — do not generate from scratch; do not omit $lStatus / _Resolve / iterator-delete conventions
  5. Assemble using the user's specific refdes / paths / package names, and return a single self-contained .tcl tailored to this request
  6. Include execution steps: which .DSN to open → which page to navigate to → which snippet to paste into the Command Window → expected log signals

Read the full file on GitHub · 58 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. 8d ago First seen · 58 lines · 109 tokens per session scan A 2c8bce3c8dcf

Subscribe to this mod's changes

automating-orcad-capture-tcl is a skill published in the GitHub repository redstone39/orcad-capture-toolkit (6 stars, last pushed 4mo ago), licensed MIT. It adds 109 tokens to every session and 944 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-31.

Related

Other skills, from other repositories

kicad

Analyze KiCad projects and PDF schematics: schematics, PCB layouts, Gerbers, footprints, symbols, netlists, and design rules. Reviews designs for bugs, traces nets, cross-references schematic to PCB, extracts BOM data, checks DRC/ERC, DFM, power trees, and regulator circuits. Every finding carries a confidence label…

aklofas/kicad-happy · 240 tokens

digikey

Search DigiKey for electronic components and download datasheets — primary source for prototype orders and the preferred API method for fetching datasheets. Find parts by keyword or MPN, check pricing/stock, download datasheets via API, analyze specifications. Sync and maintain a local datasheets directory — extract…

aklofas/kicad-happy · 179 tokens

element14

Search Newark, Farnell, and element14 for electronic components — find parts by MPN or distributor part number, check pricing/stock, download datasheets, analyze specifications. One unified API covers all three storefronts (Newark for US, Farnell for UK/EU, element14 for APAC). Free API key, simple query-parameter…

aklofas/kicad-happy · 188 tokens

emc

EMC pre-compliance risk analysis for KiCad PCB designs — 18 check categories, 44 rule IDs covering ground planes, decoupling, I/O filtering, switching harmonics, clock routing, differential pair skew, board edge radiation, PDN impedance, return paths, crosstalk, ESD protection, shielding, and magnetic leakage from…

aklofas/kicad-happy · 214 tokens

jlcpcb

JLCPCB PCB fabrication and assembly — BOM/CPL generation, basic vs extended parts, assembly constraints, design rules, ordering workflow. Use with KiCad for JLCPCB manufacturing. Use this skill when the user mentions JLCPCB, wants to order PCBs or assembled boards, needs prototype bare PCBs and stencils, wants to know…

aklofas/kicad-happy · 113 tokens

mouser

Search Mouser Electronics for electronic components — secondary source for prototype orders. Find parts, check pricing/stock, download datasheets, analyze specifications. Use with KiCad for BOM creation and part selection. Also supports batch MPN-list seeding (--mpn-list) for bulk datasheet workflows without a KiCad…

aklofas/kicad-happy · 125 tokens