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 redstone39/orcad-capture-toolkit --skill orcad-capture-toolkitgit clone --depth 1 https://github.com/redstone39/orcad-capture-toolkitWrote 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/redstone39/orcad-capture-toolkit/orcad-capture-toolkit)<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.
<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>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.00109 | $0.00944 |
| Opus 5.5 | $0.00044 | $0.00378 |
| Sonnet 5.5 | $0.00022 | $0.00189 |
| Haiku 4.5 | $0.00011 | $0.00094 |
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 1mo 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 — 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
- Read
references/ai-usage.md— decision tree + output specification + composable idiom building blocks (primary entry point) - Read the relevant
references/module — verify viable APIs, known pitfalls, and version dependencies - Check
references/anti-patterns.md— confirm the APIs you intend to use are not on the DO NOT list - Build on the §5 idiom blocks in ai-usage.md — do not generate from scratch; do not omit
$lStatus/_Resolve/ iterator-delete conventions - Assemble using the user's specific refdes / paths / package names, and return a single self-contained
.tcltailored to this request - Include execution steps: which .DSN to open → which page to navigate to → which snippet to paste into the Command Window → expected log signals
What ships with it
5 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.
- 1mo ago First seen · 58 lines · 109 tokens per session scan A 2c8bce3c8dcf
automating-orcad-capture-tcl is a skill published in the GitHub repository redstone39/orcad-capture-toolkit (12 stars, last pushed 6mo ago), licensed MIT. It adds 109 tokens to every session and 944 once invoked, about $0.0004 per session on Opus 5.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.
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…
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…
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…
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…
lcsc
Search LCSC Electronics for electronic components — find parts by LCSC number (Cxxxxx) or MPN, check stock/pricing, download datasheets, analyze specifications. Sister company to JLCPCB, same parts library. Sync and maintain a local datasheets directory for a KiCad project, or use batch MPN-list seeding (--mpn-list)…
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…