Borrowing it
Nothing to install: this file belongs to circuit-synth/kicad-sch-api. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/circuit-synth/kicad-sch-api/main/.claude/commands/dev/dev.mdgit clone --depth 1 https://github.com/circuit-synth/kicad-sch-apiWrote 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/commands/circuit-synth/kicad-sch-api/dev)<a href="https://agentmods.dev/commands/circuit-synth/kicad-sch-api/dev"><img src="https://agentmods.dev/badge/commands/circuit-synth/kicad-sch-api/dev/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/commands/circuit-synth/kicad-sch-api/dev"><img src="https://agentmods.dev/badge/commands/circuit-synth/kicad-sch-api/dev.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.00013 | $0.10083 |
| Opus 5.5 | $0.00005 | $0.04033 |
| Sonnet 5.5 | $0.00003 | $0.02017 |
| Haiku 4.5 | $0.00001 | $0.01008 |
Grade A, and why
dev scanned grade A with 1 finding 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 2mo 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
subprocess.run(["open", "/tmp/validation_demo.kicad_sch"]) How it starts
The opening of the file, as written. The whole thing — 1,314 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/dev - Development Workflow for KiCAD Schematic API
Purpose: Complete development workflow from problem description to pull request, using KiCAD reference-driven development with comprehensive testing and format preservation validation.
Use when: Building features, fixing bugs, or adding functionality that requires systematic development with PRD, reference schematics, tests, and iterative implementation.
Workflow Overview
/dev (end-to-end development)
├─ Phase 1: Generate PRD (research → ask questions → document)
│ └─ STOP: User reviews PRD
├─ Phase 2: Create Reference Schematic (Interactive - agent creates, user refines)
│ └─ STOP: User edits in KiCAD, says "done"
├─ Phase 3: Generate Tests (autonomous - no stop)
├─ Phase 4: Implementation (autonomous + communicative - shows progress)
│ └─ STOP if stuck after 8 iterations
├─ Phase 4.5: Manual Validation (Interactive - agent guides, user inspects)
│ └─ STOP: User validates in KiCAD
└─ Phase 5: Cleanup & PR (autonomous - no stop)
Time estimate: 1-4 hours depending on complexity
Reviewing and Fixing Existing PRs
If you encounter an existing PR with failing CI, follow these steps to fix it:
Step 1: Checkout the PR branch
gh pr checkout {PR_NUMBER}
Step 2: Fix formatting issues
# Format code
uv run black kicad_sch_api/ tests/
uv run isort kicad_sch_api/ tests/
Step 3: Fix other CI failures
# Run tests to identify failures
uv run pytest tests/ -v
# Fix type errors
uv run mypy kicad_sch_api/
# Fix linting issues
uv run flake8 kicad_sch_api/ tests/
Step 4: Commit and push fixes
git add -A
git commit -m "chore: Fix CI formatting and test failures
Apply black and isort formatting to pass CI checks.
Fix any test failures and type errors.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <[email protected]>"
git push origin {BRANCH_NAME}
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.
- 2mo ago First seen · 1,314 lines · 13 tokens per session scan A 73023d9c1270
dev is a command published in the GitHub repository circuit-synth/kicad-sch-api (57 stars, last pushed 10mo ago), licensed MIT. It adds 13 tokens to every session and 10,083 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
_anti_fabrication_rules
Codified after the v10627 / v10627-vendor false-PASS comparison. Inlined into every phase2 / phase2 / phase3 / phase23 / vibe-ic-all command so that any fresh agent invoking those commands sees the same hard rules.
pcb-new
Start a new PCB project from a text description. Sources parts, generates a wired .kicadpcb, and hands off to EasyEDA for routing + JLCPCB ordering.
pcb-from-bom
Start a PCB project from an existing LCSC BOM file (CSV with C-numbers) and a design-intent description.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.