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 agentmods add skills/milind220/ki-stack/ki-stack-symbolsnpx skills add Milind220/Ki-Stack --skill ki-stack-symbolsgit 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-symbols)<a href="https://agentmods.dev/skills/milind220/ki-stack/ki-stack-symbols"><img src="https://agentmods.dev/badge/skills/milind220/ki-stack/ki-stack-symbols.svg" alt="Measured on agentmods" 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 | $0.00045 | $0.00783 |
| Opus 5 | $0.00023 | $0.00392 |
| Sonnet 5 | $0.00009 | $0.00157 |
| Haiku 4.5 | $0.00005 | $0.00078 |
Grade A, and why
ki-stack-symbols 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 4d 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ki-stack-symbols
Purpose
This Phase 2 domain skill orchestrates symbol-focused work by composing:
ki-stack-renderki-stack-file-surgeryki-stack-verify
Use it when the user's intent is specifically about symbols or symbol libraries.
What it covers
- symbol rendering
- symbol library inspection
- symbol-side offline edits and regeneration workflows
- symbol verification through exports
Routing rules
Use ki-stack-render when
- the user wants to inspect or compare a symbol visually
- the task is to export symbol artifacts
Use ki-stack-file-surgery when
- the symbol task is a deterministic library or file transform
- preserving file structure and tokens matters
Use ki-stack-verify after
- any symbol edit that should be proven visually
Phase 1: Orient
- Confirm the task is symbol-scoped.
- Identify the
.kicad_symfile and exact symbol name. - If the symbol name is missing, stop and ask for it or search the library contents first.
Phase 2: Inspect
The most useful first step is usually rendering the target symbol.
Canonical command:
skills/ki-stack/bin/kicad-render symbol-svg library.kicad_sym out_dir --symbol Device:R
If the task is an offline edit, inspect the relevant library files before mutation.
Phase 3: Execute
For symbol work in v1, prefer deterministic offline workflows over speculative live APIs.
Common execution path:
- identify the symbol library file
- render the baseline symbol
- apply the symbol-side change offline
- render the symbol again
- report before/after artifacts
Phase 4: Verify
The main proof for symbol tasks is visual and export-based.
Prefer:
- render before
- change symbol
- render after
- report both artifact paths
If the task affects downstream library behavior, note any limits in verification.
Common symbol workflows
Workflow: inspect a symbol visually
- render the symbol as SVG
- convert to PNG if a raster artifact is needed
- report the artifact path
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.
- 4d ago First seen · 138 lines · 45 tokens per session scan A 02db89bb0074
ki-stack-symbols is a skill published in the GitHub repository Milind220/Ki-Stack (12 stars, last pushed 3mo ago), licensed MIT. It adds 45 tokens to every session and 783 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.
Other skills, from other repositories
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.
zaptrace-design-validation
Validate a local ZapTrace design with requirements review, ERC/DRC evidence, and bounded engineering risk reports without claiming fabrication approval.
boardrepo
Read and review real PCB projects on BoardRepo. Search published hardware designs, open a board's schematic connectivity, bill of materials and files, run KiCad's DRC and ERC, and check a design against a fabrication house's limits. Use whenever the user names a BoardRepo board or URL, asks to find a published board…
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-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".