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 commands/circuit-synth/kicad-sch-api/create-schematicgit clone --depth 1 https://github.com/circuit-synth/kicad-sch-apiWhat 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.00012 | $0.01274 |
| Opus 5 | $0.00006 | $0.00637 |
| Sonnet 5 | $0.00002 | $0.00255 |
| Haiku 4.5 | $0.00001 | $0.00127 |
Grade A, and why
create-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 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 — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Schematic Command
Generate a complete KiCAD schematic file from a natural language description using kicad-sch-api.
Usage
/create-schematic <description>
Examples
# Simple circuit
/create-schematic "voltage divider with two 10k resistors"
# Power supply
/create-schematic "3.3V voltage regulator circuit with AMS1117 and bypass capacitors"
# LED circuit
/create-schematic "LED circuit with 330 ohm resistor and 5V power supply"
# More complex
/create-schematic "ESP32-C3 dev board with USB-C, voltage regulator, and reset button"
What This Does
This command:
- Analyzes your circuit description
- Selects appropriate components from KiCAD libraries
- Creates schematic with proper component placement
- Adds pin-to-pin wiring connections
- Sets component properties (values, footprints, etc.)
- Saves to a .kicad_sch file in current directory
- Provides summary of components used
Implementation
When you provide a circuit description, I will:
1. Parse Requirements
- Identify required components (resistors, capacitors, ICs, etc.)
- Determine component values from description
- Identify connections and topology
2. Select Components
# Select appropriate KiCAD library components
# Device:R for resistors
# Device:C for capacitors
# Device:LED for LEDs
# Regulator_Linear:AMS1117-3.3 for voltage regulators
# RF_Module:ESP32-C3-MINI-1 for ESP32
# etc.
3. Generate Schematic
import kicad_sch_api as ksa
# Create schematic with descriptive title
sch = ksa.create_schematic("Circuit Name from Description")
# Add components with proper spacing
# Position components logically (left to right: input -> processing -> output)
# Add appropriate footprints for each component
# Wire components together
# Use pin-to-pin wiring for automatic routing
# Add power symbols and ground connections
# Add labels for important nets
# Set component properties (tolerance, power rating, etc.)
# Save to file
sch.save("circuit_name.kicad_sch")
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 · 195 lines · 12 tokens per session scan A 0e60e4258f1e
create-schematic is a command published in the GitHub repository circuit-synth/kicad-sch-api (51 stars, last pushed 9mo ago), licensed MIT. It adds 12 tokens to every session and 1,274 once invoked, about $0.0001 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-30.
Other commands, from other repositories
run-reference-tests
Command "run-reference-tests" from richard-luc/KiCAD-Schematic-Manipulation, covering reference schematic tests command - kicad-sch-api, usage, description, parameters and reference project structure.
review-implementation
Command "review-implementation" from richard-luc/KiCAD-Schematic-Manipulation, covering review implementation command - kicad-sch-api, usage, description, parameters and review areas.
vibe-ic-benchmark
Run any known open IC-design benchmark (VerilogEval-v2/Human, RTLLM, CVDP, …) the CORRECT way per the open-benchmark-methodology skill. Auto-routes to the right run-shape (A/B/C/D), sets up the run dir scaffold, points at the blind instructions, and invokes the scorer. Use when "run benchmark X", "score benchmark X"…
vibe-ic-all
Run the complete Vibe-IC flow (Phase 1 → Phase 2 → Analog → Phase 3) via vibeiconeshotrunner. Auto-detects Path A vs B. AI-monitored + close-loop.
vibe-ic-phase2
Run Phase 2 (L1-L27 → RTL → SOF → byte[6]=0xF2) via designoneshotrunner. AI-monitored + bounded RTL repair/retry.
vibe-ic-phase3
Run Phase 3 (synth → PnR → GDS → DRC → LVS) via phase3oneshotrunner. AI-monitored + close-loop.