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 instructions/vonpanda/schematic-mcp/agents-mdgit clone --depth 1 https://github.com/vonpanda/schematic-mcpWhat 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.00911 | $0.00911 |
| Opus 5 | $0.00456 | $0.00456 |
| Sonnet 5 | $0.00182 | $0.00182 |
| Haiku 4.5 | $0.00091 | $0.00091 |
Grade A, and why
schematic-mcp AGENTS.md 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 yesterday.
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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This file gives coding agents and human contributors the project rules that matter most when changing schematic-mcp.
Project goal
schematic-mcp is a hardware-context server for AI agents. It converts EDA schematics into a deterministic, format-neutral component/pin/net model and exposes that model through MCP.
The project is not trying to become a general-purpose KiCad GUI automation layer or an autorouter. The long-term direction is read-oriented hardware context, cross-EDA adapters, electrical reasoning, and firmware ↔ schematic validation.
Architecture
src/schematic_mcp/parsers/— EDA-specific adapters. New formats should terminate in the canonical model rather than leak format-specific behavior into MCP tools.src/schematic_mcp/models.py— canonical data structures.src/schematic_mcp/graph.py— deterministic graph/query helpers over the canonical model.src/schematic_mcp/workspace.py— current loaded schematic and filesystem boundary enforcement.src/schematic_mcp/server.py— MCP tools/resources and CLI transport setup.examples/— synthetic or explicitly redistributable fixtures only.tests/— behavior and regression tests.
Read docs/architecture.md before making parser/model changes.
Required development loop
From a clean checkout:
python -m venv .venv
source .venv/bin/activate
pip install -e ".[dev]"
pytest
python -m build
On Windows, use the appropriate virtual-environment activation command instead of source.
Every behavior change should add or update tests. Parser bugs should be reduced to the smallest safe fixture that reproduces the issue.
Electrical correctness invariants
- Never invent connectivity. If the file does not provide enough information to resolve a connection, preserve an unknown state or emit a warning.
- Do not infer internal IC connectivity.
trace_signalfollows resolved schematic nets only. - Keep parser behavior deterministic. The same file should produce the same canonical model without an LLM call.
- Preserve ambiguity. Duplicate labels, ambiguous pin names, unsupported constructs, and unresolved hierarchy should be surfaced explicitly rather than silently normalized away.
- Prefer exact source evidence. When adding future confidence-based adapters such as PDF parsing, attach confidence/source metadata rather than presenting uncertain results as exact net connectivity.
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.
- yesterday First seen · 95 lines · 911 tokens per session scan A dd1eadb22a9c
schematic-mcp AGENTS.md is an instructions file published in the GitHub repository vonpanda/schematic-mcp (0 stars, last pushed 14d ago), licensed Apache-2.0. It adds 911 tokens to every session, about $0.0046 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 instructions, from other repositories
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.