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/review-implementationgit 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/review-implementation)<a href="https://agentmods.dev/commands/circuit-synth/kicad-sch-api/review-implementation"><img src="https://agentmods.dev/badge/commands/circuit-synth/kicad-sch-api/review-implementation.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.00000 | $0.01316 |
| Opus 5 | $0.00000 | $0.00658 |
| Sonnet 5 | $0.00000 | $0.00263 |
| Haiku 4.5 | $0.00000 | $0.00132 |
Grade A, and why
review-implementation 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- review-implementation — 100% identical, 0 lines differ
- review-implementation — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review Implementation Command - kicad-sch-api
Usage
/review-implementation [component]
Description
Performs comprehensive code review and analysis of kicad-sch-api implementation, focusing on professional quality, performance, and API design.
Parameters
component(optional): Specific component to review (core,library,mcp,utils,tests)--performance: Focus on performance analysis--api-design: Focus on API usability review--format-preservation: Focus on format preservation validation
Review Areas
1. Core Library Review
/review-implementation core
Focuses on:
- S-expression parsing accuracy and performance
- Component management API design and efficiency
- Schematic operations completeness and validation
- Type system correctness and usability
- Error handling comprehensiveness and clarity
Key Questions:
- Does the API feel intuitive and pythonic?
- Are bulk operations efficient for large schematics?
- Is format preservation truly exact?
- Do validation errors provide actionable feedback?
2. Library Management Review
/review-implementation library
Focuses on:
- Symbol caching performance and accuracy
- Library discovery robustness across platforms
- Multi-source integration (future: DigiKey, SnapEDA)
- Cache invalidation and persistence
Key Questions:
- Does caching provide measurable performance improvement?
- Is library discovery reliable across different KiCAD installations?
- Are cache miss scenarios handled gracefully?
3. MCP Integration Review
/review-implementation mcp
Focuses on:
- Tool completeness for AI agent workflows
- Error handling quality for agent consumption
- Python bridge reliability and performance
- TypeScript integration professional standards
Key Questions:
- Do MCP tools cover all essential schematic operations?
- Are error messages clear enough for AI agents to understand?
- Is the Python bridge robust against subprocess failures?
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 · 172 lines · 0 tokens per session scan A a55e90ed0404
review-implementation is a command published in the GitHub repository circuit-synth/kicad-sch-api (52 stars, last pushed 9mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,316 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 commands, from other repositories
review-branch
Purpose: Comprehensive branch analysis for code quality, security, performance, and risk assessment before merging to main. Specialized for circuit-synth development workflows.
dead-code-analysis
Command "dead-code-analysis" from circuit-synth/circuit-synth, covering dead code analysis command, usage, description, parameters and output files.
bug
Debug and fix issues with log-driven iterative approach.
make-test
Wrap manual test into automated pytest test.
review-prompt
Review prompts for best practices and clarity.
test-ref
Create reference material for testing and development.