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/fireostendere/mcp_diptrace/agents-mdgit clone --depth 1 https://github.com/fireostendere/mcp_diptraceWrote 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/instructions/fireostendere/mcp_diptrace/agents-md)<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>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.1 | $0.00816 | $0.00816 |
| Opus 5 | $0.00408 | $0.00408 |
| Sonnet 5 | $0.00163 | $0.00163 |
| Haiku 4.5 | $0.00082 | $0.00082 |
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.
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.
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.
- 6d ago First seen · 65 lines · 816 tokens per session scan A 98ed62344e94
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.
Other instructions, from other repositories
cml-mcp AGENTS.md
AGENTS.md instructions for xorrkaz/cml-mcp, covering agents.md — cml mcp server, project overview, compatibility goal, repository layout and tool modules (src/cmlmcp/tools/).
brilliant_sdk AGENTS.md
Instructions for brilliantlabsAR/brilliant_sdk, covering brilliant sdk — agent guide, how an app works (the pattern behind everything), minimal reading paths, verify without hardware and testing.
NeoMind CLAUDE.md
Claude Code instructions for camthink-ai/NeoMind, covering neomind — edge ai platform for iot, development commands, ecosystem repositories, extension package contract (.nep) and device type template contract (json).
cad-cae-copilot copilot-instructions.md
Copilot instructions for armpro24-blip/cad-cae-copilot, covering github copilot — aieng workspace and essentials.
phone-mcp CLAUDE.md
Claude Code instructions for premex-ab/phone-mcp, covering claude.md, project overview, build commands, architecture and module layout.
zmk-config AGENTS.md
AGENTS.md instructions for urob/zmk-config, covering customization guide, ground rules, how the multi-board layout works, adding a new board and where to change what.