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 Milind220/Ki-Stack --skill ki-stack-schematicgit clone --depth 1 https://github.com/Milind220/Ki-StackWrote 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/milind220/ki-stack/ki-stack-schematic)<a href="https://agentmods.dev/skills/milind220/ki-stack/ki-stack-schematic"><img src="https://agentmods.dev/badge/skills/milind220/ki-stack/ki-stack-schematic/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/milind220/ki-stack/ki-stack-schematic"><img src="https://agentmods.dev/badge/skills/milind220/ki-stack/ki-stack-schematic.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.00052 | $0.01107 |
| Opus 5.5 | $0.00021 | $0.00443 |
| Sonnet 5.5 | $0.00010 | $0.00221 |
| Haiku 4.5 | $0.00005 | $0.00111 |
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 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 — 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-renderki-stack-file-surgeryki-stack-verifyki-stack-livewhen 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
-
Confirm the task is schematic-scoped.
-
Identify the relevant
.kicad_schand.kicad_profiles. -
Probe the environment:
skills/ki-stack/bin/kicad-version skills/ki-stack/bin/kicad-project-find <root> -
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.
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 · 184 lines · 52 tokens per session scan A 05ba94bd1a14
ki-stack-schematic is a skill published in the GitHub repository Milind220/Ki-Stack (23 stars, last pushed 4mo ago), licensed MIT. It adds 52 tokens to every session and 1,107 once invoked, about $0.0002 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
altium-designer
Automate Altium Designer PCB workflows with DXP scripts, design-rule checks, OutJob fabrication outputs, and routing configuration.
pcb-design
Design, modify, review, validate, or export a KiCad schematic or PCB from natural-language hardware requirements. Use for circuit design, component selection, schematic capture, footprint assignment, board layout, routing, ERC/DRC, BOM, Gerbers, and manufacturing handoff through the KiCad MCP tools.
kicad-copilot-mcp
Use when KiCad Copilot MCP tools are available. Entry point for KiCad schematic and PCB workflows.
kicad-schematic-design
Create, edit, inspect, and validate KiCad schematics for digital, analog, power, interface, and mixed-signal circuits. Use for requests to open KiCad, create or draw schematics, place library symbols, assign footprints, define external interfaces, wire nets, review screenshots, or diagnose ERC and netlist issues.
kicad-library
Library management workflow for KiCAD — creating symbols, footprints, and managing libraries via MCP tools. Triggers on: "create a symbol", "make a footprint", "custom component", "register library", "find a part", "pin numbering", "new symbol", "new footprint", "add to library", "library path", "pad layout".
kicad-review
Design review and validation workflow for KiCAD projects via MCP tools. Triggers on: "review my design", "check for errors", "audit", "DRC", "ERC", "find problems", "design review", "is this ready", "validate", "check my schematic", "check my PCB", "what's wrong", "run checks", "pre-fab review".