agentmods.dev

ki-stack-verify

A verification workflow for KiCad electronics projects after a change. KiCad is software for designing circuit schematics and printed circuit boards, or PCBs.

In plain words
What is it for?
It helps verify board and schematic edits, render visual evidence, run PCB design-rule checks, run schematic electrical-rule checks, and report exact results.
Why use it?
A file edit may look correct in text while still producing a broken schematic or board. This checks the result with renders and, where relevant, design-rule or electrical-rule checks.

Skill for Claude CodeCodex

8 +1 3mo ago A scan 48 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-verify
Any agent
npx skills add Milind220/Ki-Stack --skill ki-stack-verify
Clone the repo
git clone --depth 1 https://github.com/Milind220/Ki-Stack

Made for: Claude Code, Codex.

Per session 48 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,192 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.00048 $0.01192
Opus 5 $0.00024 $0.00596
Sonnet 5 $0.00010 $0.00238
Haiku 4.5 $0.00005 $0.00119

Measured 2d ago against content hash 46003338628b, 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-verify 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-verify/SKILL.md · 196 lines

How it starts

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

ki-stack-verify

Purpose

This skill teaches the agent how to prove that a KiCad change actually worked.

It is the canonical ki-stack skill for:

  • render-after-edit verification
  • PCB DRC
  • schematic ERC when relevant
  • export/check loops
  • evidence-first reporting

When to use it

Use this skill after:

  • a live IPC edit
  • an offline kiutils-rs transform
  • a manual KiCad file change that needs proof
  • any task where visual and structural correctness matters

Shared assumptions

  • A change is not done until there is evidence.
  • Prefer deterministic exports over subjective descriptions.
  • Prefer CLI checks when available.
  • Report exact outputs, not just impressions.

Phase 1: Orient

  1. Determine the artifact type that changed:
  • board
  • schematic
  • symbol
  • footprint
  • project metadata only

  1. Confirm KiCad CLI availability:

    skills/ki-stack/bin/kicad-cli-path
skills/ki-stack/bin/kicad-version

  2. Decide which evidence applies:

  • visual render
  • DRC
  • ERC
  • file re-inspection
  • a combination of the above

Phase 2: Render evidence

If the change affects anything visual, render it.

Examples:

Board before/after

skills/ki-stack/bin/kicad-render pcb-svg board.kicad_pcb before_dir --layers F.Cu,F.SilkS,Edge.Cuts --mode-single
skills/ki-stack/bin/kicad-render pcb-svg board.kicad_pcb after_dir --layers F.Cu,F.SilkS,Edge.Cuts --mode-single

Board 3D proof

skills/ki-stack/bin/kicad-render pcb-render board.kicad_pcb board.png --width 1800 --height 1200 --side top

Schematic proof

skills/ki-stack/bin/kicad-render schematic-svg design.kicad_sch out_dir

Symbol or footprint proof

skills/ki-stack/bin/kicad-render symbol-svg library.kicad_sym out_dir --symbol Device:R
skills/ki-stack/bin/kicad-render footprint-svg my.pretty out_dir --footprint SOIC-8_3.9x4.9mm_P1.27mm

Phase 3: Run machine checks

PCB DRC

Preferred command:

skills/ki-stack/bin/kicad-drc-json board.kicad_pcb drc.json

Read the full file on GitHub · 196 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 · 196 lines · 48 tokens per session scan A 46003338628b

Subscribe to this mod's changes

ki-stack-verify is a skill published in the GitHub repository Milind220/Ki-Stack (8 stars, last pushed 3mo ago), licensed MIT. It adds 48 tokens to every session and 1,192 once invoked, about $0.0002 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.

Hardware and IoTagent-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