agentmods.dev

ki-stack-schematic

A workflow for KiCad schematic projects, including sheet rendering and electrical-rule checking. A schematic is the diagram that shows how electronic components connect before a circuit board is made.

In plain words
What is it for?
Use it to find and inspect schematic files, render sheets, run ERC checks, manage project text variables, and verify schematic edits.
Why use it?
It combines schematic inspection and checks so design changes can be reviewed visually and tested for electrical mistakes.

Skill for Claude CodeCodex

8 +1 3mo ago A scan 52 tokens original MIT
View the source file Milind220/Ki-Stack
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.

agentmods
npx agentmods add skills/milind220/ki-stack/ki-stack-schematic
Any agent
npx skills add Milind220/Ki-Stack --skill ki-stack-schematic
Clone the repo
git clone --depth 1 https://github.com/Milind220/Ki-Stack

Made for: Claude Code, Codex.

Per session 52 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,107 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00052 $0.01107
Opus 5 $0.00026 $0.00553
Sonnet 5 $0.00010 $0.00221
Haiku 4.5 $0.00005 $0.00111

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

Security

Grade A, and why

ki-stack-schematic 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 2d 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.

skills/ki-stack/ki-stack-schematic/SKILL.md · 184 lines

How it starts

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

ki-stack-schematic

Purpose

This Phase 2 domain skill orchestrates schematic-focused work by composing:

  • ki-stack-render
  • ki-stack-file-surgery
  • ki-stack-verify
  • ki-stack-live when schematic-side IPC support is relevant in the environment

Use this skill when the user's intent is clearly about schematics rather than boards.

What it covers

  • rendering schematic sheets and full schematics
  • schematic ERC
  • project text variable workflows
  • schematic file discovery and inspection
  • proof-oriented schematic change verification

Routing rules

Use ki-stack-render when

  • the user wants to see a schematic page or export it
  • the task is primarily visual
  • the goal is proof, documentation, or comparison

Use ki-stack-file-surgery when

  • the schematic-side task is a deterministic file transformation
  • the task is project-file or metadata oriented
  • no live editor context is required

Use ki-stack-live when

  • the environment exposes the needed schematic-side API surface
  • the task genuinely benefits from live project/editor state

Use ki-stack-verify after

  • schematic changes that could affect electrical correctness
  • any schematic edit that needs before/after proof

Phase 1: Orient

  1. Confirm the task is schematic-scoped.

  2. Identify the relevant .kicad_sch and .kicad_pro files.

  3. Probe the environment:

    skills/ki-stack/bin/kicad-version
skills/ki-stack/bin/kicad-project-find <root>

  4. Decide the path:

  • render-only
  • offline file/proj transform
  • live API path if the environment supports it

Phase 2: Inspect

For schematic tasks, inspect the available files and identify page scope before editing.

Helpful checks:

skills/ki-stack/bin/kicad-project-find <root>

For project-side text variables, the kicad-python project object exposes:

  • get_text_variables()
  • set_text_variables()
  • expand_text_variables()

If the task is visual, render a baseline artifact first.

Read the full file on GitHub · 184 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. 2d ago First seen · 184 lines · 52 tokens per session scan A 05ba94bd1a14

Subscribe to this mod's changes

ki-stack-schematic is a skill published in the GitHub repository Milind220/Ki-Stack (8 stars, last pushed 3mo ago), licensed MIT. It adds 52 tokens to every session and 1,107 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-31.

PlanningProductivityagent-skillsai-agentselectronics-automationkicadpcb-design
Related

Other skills, from other repositories

plan-pcb-routing

Analyzes a KiCad PCB file and creates a comprehensive routing plan. Examines components for fanout needs (BGA/QFN/QFP/PGA), identifies differential pairs, categorizes power/ground nets, and presents a step-by-step routing workflow with explanations.

drandyhaas/KiCadRoutingTools · 58 tokens

plan-pcb-placement-and-routing

Plans a KiCad PCB end to end when ONE run must both place and route it. Sequences the placement skill and the routing skill, and owns the rules that exist only when the two meet: that placement invalidates every downstream routed board, that a routing failure must be classified before it is retried, and that a…

drandyhaas/KiCadRoutingTools · 103 tokens

plan-pcb-placement

Analyses a KiCad PCB's PLACEMENT and produces a placement plan. Measures whether the board should be placed or re-placed at all and decides from that measurement, detects an unplaced board, separates the parts whose position is a mechanical fact from the ones a search may move, reconstructs a damaged placement…

drandyhaas/KiCadRoutingTools · 115 tokens

find-high-speed-nets

Analyzes a KiCad PCB to identify high-speed and impedance-controlled nets by looking up component datasheets via AI. Classifies nets by speed tier (ultra-high/high/medium/low), detects RF/antenna feeds and other controlled-impedance nets, estimates max frequencies and rise times per interface, and recommends GND…

drandyhaas/KiCadRoutingTools · 133 tokens

review-routed-board

Post-route QA on a KiCad board. Runs the DRC, connectivity, and orphan-stub checkers, verifies length/time-match groups landed within tolerance, checks GND return via coverage on high-speed nets, and reviews differential pairs. Produces a pass/fail sign-off report with concrete next actions. Works on boards routed by…

drandyhaas/KiCadRoutingTools · 83 tokens

stress-test-router

Stress-tests the router against real-world open-source KiCad boards (downloaded, normalized, stripped of routing), measuring routing completion rates and DRC violations per board. Aggregates results and files GitHub issues for new router/parser findings after user approval. Use to regression-test the router at scale…

drandyhaas/KiCadRoutingTools · 69 tokens