pcb AGENTS.md

A set of project instructions for diodeinc/pcb, a Rust-based tool for building and testing Zener electronic designs. It explains the PCB command-line tools, development workflow, and important source locations.

In plain words
What is it for?
Use it when building, testing, formatting, or generating KiCad layouts for Zener designs, or when changing the Rust and Python parts of the project.
Why use it?
It gives a coding agent the project rules and commands needed to work consistently without guessing where code belongs or how to validate changes.

Instructions file for CodexOpenCode

Install

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.

agentmods
npx agentmods add instructions/diodeinc/pcb/agents-md
Clone the repo
git clone --depth 1 https://github.com/diodeinc/pcb

Made for: Codex, OpenCode.

Per session 1,062 This file is loaded in full into every session.
When invoked 1,062 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 2d ago against content hash ed7d9fa6e431, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

AGENTS.md · 56 lines

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 .zen files.
  • cargo run -p pcbc -- fmt [PATHS...] — format .zen files.
  • 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 changing crates/pcb-layout/src/scripts/lens/.

Never run cargo insta accept without explicit user approval.

Where to Look

  • Start with README.md for product context and user-facing CLI behavior.
  • crates/pcb/src/main.rs is the shim/version manager; crates/pcbc/src/main.rs declares compiler CLI subcommands, with matching files in crates/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. Check docs/pages/spec.mdx when changing user-visible language behavior.
  • crates/pcb-zen/src/ provides higher-level workspace/dependency resolution, package cache, diagnostics plumbing, and LSP integration around pcb-zen-core.
  • crates/pcb-sch/src/ is the schematic/netlist data model, BOM helpers, KiCad netlist export, and # pcb:sch comment handling.
  • crates/pcb-layout/src/ generates and synchronizes KiCad layouts. The Python lens implementation is in crates/pcb-layout/src/scripts/lens/; read crates/pcb-layout/README.md before 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/ implements pcb import; start with crates/pcbc/src/import/README.md and flow.rs before changing the import pipeline.
  • crates/pcb-eda/ and crates/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/ and test-workspaces/ are useful runnable designs.
  • Use docs/pages/packages.mdx for workspace, dependency, and package behavior.

Read the full file on GitHub · 56 lines

Changes

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.

  1. 2d ago First seen · 56 lines · 1,062 tokens per session scan A ed7d9fa6e431

Subscribe to this mod's changes

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.

Related

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.

github/spec-kit · 7,104 tokens

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.

openai/codex · 5,182 tokens

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).

microsoft/vscode · 6,785 tokens

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.

langchain-ai/langchain · 4,345 tokens

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).

microsoft/vscode · 5,001 tokens

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.

vercel/next.js · 7,296 tokens