mcp_diptrace AGENTS.md

mcp_diptrace AGENTS.md is an instructions file for Codex, OpenCode from fireostendere/mcp_diptrace. It costs 816 tokens per session, scanned A, original, Apache-2.0.

Repository instructions for creating printed circuit boards, including component footprints, placement, routing, grounding, and manufacturing constraints. They require checking official datasheets before using physical parts.

In plain words
What is it for?
Use them when generating PCB layouts or demonstration media, especially to verify packages, follow vendor layouts, keep boards compact, route two-layer boards, and document intentional deviations.
Why use it?
They provide consistent PCB build and handoff rules while making missing electrical or mechanical evidence a reason to stop.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md.

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/fireostendere/mcp_diptrace/agents-md
Clone the repo
git clone --depth 1 https://github.com/fireostendere/mcp_diptrace

Made for: Codex, OpenCode.

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

agentmods badge for mcp_diptrace AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/fireostendere/mcp_diptrace/agents-md.svg)](https://agentmods.dev/instructions/fireostendere/mcp_diptrace/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/fireostendere/mcp_diptrace/agents-md"><img src="https://agentmods.dev/badge/instructions/fireostendere/mcp_diptrace/agents-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 816 This file is loaded in full into every session.
When invoked 816 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.1 $0.00816 $0.00816
Opus 5 $0.00408 $0.00408
Sonnet 5 $0.00163 $0.00163
Haiku 4.5 $0.00082 $0.00082

Measured 6d ago against content hash 98ed62344e94, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

mcp_diptrace 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 6d 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 · 65 lines

How it starts

The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Repository instructions

User-taught PCB house rules

Apply these defaults to PCB generation and demonstration media unless the user explicitly requests otherwise. Datasheets, electrical safety, DRC, mechanical constraints, and manufacturability take precedence.

  • For standard 2.54 mm connectors, choose the simplest, smallest practical footprint by default.
  • Before placing any physical part, verify its exact manufacturer package and land pattern against the official datasheet. For ICs, also extract the current layout guidelines/example and check the datasheet revision history. Treat the vendor layout topology as the default constraint; document every intentional deviation and its consequence. Missing evidence blocks the PCB build.
  • Keep boards compact. Derive the outline from component courtyards plus a sane manufacturing margin, remove unused space, center the layout, and preserve visual symmetry when it does not harm placement or routing. A connector's occupied dimension may define the corresponding board dimension.
  • On ordinary two-layer boards, route signals and positive power on Top. Keep Bottom as an effectively continuous GND plane; also pour GND on Top. Break the Bottom plane only when a necessary via or physical constraint requires it.
  • Stitch Top and Bottom GND generously across every free region, not merely one edge. On small boards, start around a 2 mm grid, obey clearances, and verify coverage in every part of the board instead of relying only on the via count.
  • Connect soldered connector GND pads to pours with a four-spoke cross thermal relief so they remain easy to solder.
  • Disable via-in-pad by default. Escape each transition beyond the pad copper edge plus applicable clearance before placing the via. Allow via-in-pad only when the user explicitly requests a compatible filled/capped fabrication process.
  • Keep silkscreen readable, close to its associated component, and visually aligned. It must not enter another component's mounting/courtyard space or overlap pads, holes, or vias. Silkscreen may cross copper traces because the traces remain under solder mask.
  • For PCB and schematic recordings, show components and connections appearing one at a time in a plausible human construction order.
  • Frame recordings from the design boundary: for PCBs, use the purple board outline, fit the whole board with about 10% margin, keep the framing stable, and exclude editor controls. Apply the equivalent boundary-fit rule to schematic recordings.
  • After a visual PCB change, regenerate and inspect the PCB, MP4, and GIF. Check the final frame as well as the staged sequence.

Read the full file on GitHub · 65 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. 6d ago First seen · 65 lines · 816 tokens per session scan A 98ed62344e94

Subscribe to this mod's changes

mcp_diptrace AGENTS.md is an instructions file published in the GitHub repository fireostendere/mcp_diptrace (22 stars, last pushed 2d ago), licensed Apache-2.0. It adds 816 tokens to every session, about $0.0041 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.