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.
git clone --depth 1 https://github.com/oaslananka/kicad-mcp-proWrote 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/rules/oaslananka/kicad-mcp-pro/kicad)<a href="https://agentmods.dev/rules/oaslananka/kicad-mcp-pro/kicad"><img src="https://agentmods.dev/badge/rules/oaslananka/kicad-mcp-pro/kicad/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/rules/oaslananka/kicad-mcp-pro/kicad"><img src="https://agentmods.dev/badge/rules/oaslananka/kicad-mcp-pro/kicad.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.00000 | $0.00225 |
| Opus 5.5 | $0.00000 | $0.00090 |
| Sonnet 5.5 | $0.00000 | $0.00045 |
| Haiku 4.5 | $0.00000 | $0.00022 |
Grade A, and why
kicad 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.
What it actually says
KiCad MCP Usage
When working on KiCad projects in this repository:
- Use the
kicadMCP server for PCB and schematic operations. - Start with read-only tools before making any changes.
- Run ERC/DRC after any edit.
- Never claim manufacturing readiness without export and validation evidence.
- For design changes: explain the proposed change, ask for confirmation, then proceed.
- After changes: run ERC + DRC + DFM checks and summarize what changed.
Tool Categories
| Category | Examples | Approval |
|---|---|---|
| Read-only | kicad_get_project_info, pcb_get_board_summary, run_drc, run_erc |
Automatic |
| Write | pcb_add_*, sch_add_*, route_*, export_* |
User confirmation |
| Destructive | git_restore_checkpoint |
Explicit user approval |
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 · 25 lines · 0 tokens per session scan A 3f0b61c8054d
kicad is a cursor rule published in the GitHub repository oaslananka/kicad-mcp-pro (131 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 225 tokens. 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 cursor rules, from other repositories
kicad-happy
KiCad electronics design analysis skills — schematic review, PCB layout, EMC pre-compliance, SPICE, BOM, manufacturing.
audio-streaming
Configure and receive PCM audio with Camera Stream on iOS.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.