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-rendergit 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-render)<a href="https://agentmods.dev/skills/milind220/ki-stack/ki-stack-render"><img src="https://agentmods.dev/badge/skills/milind220/ki-stack/ki-stack-render/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-render"><img src="https://agentmods.dev/badge/skills/milind220/ki-stack/ki-stack-render.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.00063 | $0.01227 |
| Opus 5.5 | $0.00025 | $0.00491 |
| Sonnet 5.5 | $0.00013 | $0.00245 |
| Haiku 4.5 | $0.00006 | $0.00123 |
Grade A, and why
ki-stack-render 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 — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ki-stack-render
Purpose
This skill teaches the agent how to turn KiCad design artifacts into visual outputs.
It is the canonical ki-stack skill for:
- schematic rendering
- PCB 2D rendering
- PCB 3D raster rendering
- symbol rendering
- footprint rendering
- SVG to PNG conversion when raster images are needed
- before/after visual verification
When to use it
Use this skill when the user asks to:
- render a schematic sheet or whole schematic
- render a board or a specific layer set
- get a visual look at a symbol or footprint
- export PDF or SVG deliverables
- generate a PNG/JPEG screenshot-like artifact
- verify that a change actually looks correct
Shared assumptions
- Prefer
kicad-clias the default render path. - Prefer deterministic exports over GUI screenshots.
- If the model needs raster images and the CLI emits SVG, convert the SVG to PNG.
- Always report exact command lines and output paths.
Phase 1: Orient
-
Locate
kicad-cli:skills/ki-stack/bin/kicad-cli-path -
Detect the version:
skills/ki-stack/bin/kicad-version -
If the input path is unclear, find likely KiCad files:
skills/ki-stack/bin/kicad-project-find <root>
Phase 2: Identify render target
Choose one of these target classes:
- schematic
- pcb-2d
- pcb-3d
- symbol
- footprint
Map the request to the target class before choosing the command.
Examples:
- "Show me this board" ->
pcb-2dorpcb-3d - "Render this symbol" ->
symbol - "Give me a screenshot of the footprint" ->
footprint - "Visualize page 2 of the schematic" ->
schematic
Phase 3: Render
Use the helper wrapper whenever possible.
Schematic SVG
skills/ki-stack/bin/kicad-render schematic-svg design.kicad_sch out_dir
Schematic PDF
skills/ki-stack/bin/kicad-render schematic-pdf design.kicad_sch design.pdf
PCB SVG
skills/ki-stack/bin/kicad-render pcb-svg board.kicad_pcb out_dir --layers F.Cu,F.SilkS,Edge.Cuts --mode-single
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 · 198 lines · 63 tokens per session scan A 7be83ef523fb
ki-stack-render is a skill published in the GitHub repository Milind220/Ki-Stack (23 stars, last pushed 4mo ago), licensed MIT. It adds 63 tokens to every session and 1,227 once invoked, about $0.0003 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".