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/diodeinc/pcb/agents-mdgit clone --depth 1 https://github.com/diodeinc/pcbWhat 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.01062 | $0.01062 |
| Opus 5 | $0.00531 | $0.00531 |
| Sonnet 5 | $0.00212 | $0.00212 |
| Haiku 4.5 | $0.00106 | $0.00106 |
Grade A, and why
pcb 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 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
PCB CLI Subcommands
cargo run -p pcbc -- build [PATHS...]— build and validate Zener designs.cargo run -p pcbc -- test [PATHS...]— run tests declared in.zenfiles.cargo run -p pcbc -- fmt [PATHS...]— format.zenfiles.cargo run -p pcbc -- layout --no-open [PATHS...]— generate/update KiCad layout files without opening KiCad.
Development Workflow
cargo nextest run -p <crate>— run tests for one crate.cargo test --doc -p <crate>— run doctests, which nextest does not run.cargo fmt— format Rust code.uv run pytest crates/pcb-layout/src/scripts/lens/tests/ -v— run the Python layout-lens tests when changingcrates/pcb-layout/src/scripts/lens/.
Never run cargo insta accept without explicit user approval.
Where to Look
- Start with
README.mdfor product context and user-facing CLI behavior. crates/pcb/src/main.rsis the shim/version manager;crates/pcbc/src/main.rsdeclares compiler CLI subcommands, with matching files incrates/pcbc/src/(build.rs,layout.rs,fmt.rs,test.rs, etc.).crates/pcb-zen-core/src/lang/contains Zener built-ins, core values, type conversion, validation, and evaluation semantics. Checkdocs/pages/spec.mdxwhen changing user-visible language behavior.crates/pcb-zen/src/provides higher-level workspace/dependency resolution, package cache, diagnostics plumbing, and LSP integration aroundpcb-zen-core.crates/pcb-sch/src/is the schematic/netlist data model, BOM helpers, KiCad netlist export, and# pcb:schcomment handling.crates/pcb-layout/src/generates and synchronizes KiCad layouts. The Python lens implementation is incrates/pcb-layout/src/scripts/lens/; readcrates/pcb-layout/README.mdbefore changing sync behavior.crates/pcb-kicad/src/wraps KiCad tooling and KiCad-specific checks;crates/pcb-sexpr/src/handles low-level S-expression parsing/rewriting for KiCad files.crates/pcbc/src/import/implementspcb import; start withcrates/pcbc/src/import/README.mdandflow.rsbefore changing the import pipeline.crates/pcb-eda/andcrates/pcb-component-gen/handle external EDA artifacts and generated Zener component modules.crates/pcb-diode-api/contains API/auth/search/BOM-matching client logic.lib/std/contains the Zener standard library;examples/andtest-workspaces/are useful runnable designs.- Use
docs/pages/packages.mdxfor workspace, dependency, and package behavior.
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 · 56 lines · 1,062 tokens per session scan A ed7d9fa6e431
pcb AGENTS.md is an instructions file published in the GitHub repository diodeinc/pcb (434 stars, last pushed 2d ago), licensed MIT. It adds 1,062 tokens to every session, about $0.0053 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 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.
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.
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).
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.