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-footprintsnpx skills add Milind220/Ki-Stack --skill ki-stack-footprintsgit clone --depth 1 https://github.com/Milind220/Ki-StackWhat 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.00048 | $0.00931 |
| Opus 5 | $0.00024 | $0.00465 |
| Sonnet 5 | $0.00010 | $0.00186 |
| Haiku 4.5 | $0.00005 | $0.00093 |
Grade A, and why
ki-stack-footprints 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.
How it starts
The opening of the file, as written. The whole thing — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ki-stack-footprints
Purpose
This Phase 2 domain skill orchestrates footprint-focused work by composing:
ki-stack-renderki-stack-file-surgeryki-stack-verifyki-stack-livewhen the footprint is being inspected from a placed board context
Use it when the user's intent is specifically about footprints or footprint libraries.
What it covers
- footprint rendering
- footprint library inspection
- footprint-side offline edits
- visual proof of footprint changes
- placed-footprint inspection through board context when relevant
Routing rules
Use ki-stack-render when
- the user wants a visual of a footprint
- the goal is export, inspection, or before/after proof
Use ki-stack-file-surgery when
- the task is a deterministic footprint-library edit
- the change is offline and file-structural
Use ki-stack-live when
- the footprint is being investigated as a placed object on a live board
- selection or board context matters
Use ki-stack-verify after
- any footprint change that should be proven visually
Phase 1: Orient
- Confirm the task is footprint-scoped.
- Identify the
.prettylibrary directory and the exact footprint name, or identify the placed footprint on a board. - If the footprint name is unclear, stop and ask or inspect the library contents first.
Phase 2: Inspect
For library-side tasks, the first useful step is usually a visual export.
Canonical command:
skills/ki-stack/bin/kicad-render footprint-svg my.pretty out_dir --footprint SOIC-8_3.9x4.9mm_P1.27mm
For placed-footprint tasks on a live board, start with the PCB examples in ki-stack-live and ki-stack-pcb.
Phase 3: Execute
For footprint tasks in v1, prefer deterministic offline library workflows unless the request is explicitly about a placed footprint in a board context.
Common execution path:
- identify footprint library and footprint name
- render the baseline footprint
- apply the footprint-side change offline or via board context
- render again
- report before/after artifacts
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.
- 2d ago First seen · 146 lines · 48 tokens per session scan A 7099cf3a2445
ki-stack-footprints 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 931 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
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.
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…
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…
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…
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…
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…