diptrace-xml-reference

diptrace-xml-reference is a skill for Claude Code, Codex from fireostendere/mcp_diptrace. It costs 34 tokens per session (420 once invoked), scanned A, original, Apache-2.0.

Project-specific guidance for reading, writing, reviewing, and testing DipTrace XML files, which store electronic circuit-board design data. It emphasizes preserving unknown data and clearly separating tested evidence from assumptions.

In plain words
What is it for?
Use it when changing DipTrace XML parsers, writers, bridges, fixtures, or review code, and when adding tests or documenting compatibility evidence.
Why use it?
It helps avoid corrupting files, losing identifiers or unsupported fields, and making compatibility claims that the available evidence does not support.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it when changing DipTrace XML parsers, writers, bridges, fixtures, or review code, and when adding tests or documenting compatibility evidence.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/fireostendere/mcp_diptrace/diptrace-xml
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.

Any agent
npx skills add fireostendere/mcp_diptrace --skill diptrace-xml
Clone the repo
git clone --depth 1 https://github.com/fireostendere/mcp_diptrace

Made for: Claude Code, Codex.

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 diptrace-xml-reference

README.md
[![agentmods](https://agentmods.dev/badge/skills/fireostendere/mcp_diptrace/diptrace-xml/github.svg)](https://agentmods.dev/skills/fireostendere/mcp_diptrace/diptrace-xml)
Your own site
<a href="https://agentmods.dev/skills/fireostendere/mcp_diptrace/diptrace-xml"><img src="https://agentmods.dev/badge/skills/fireostendere/mcp_diptrace/diptrace-xml/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for diptrace-xml-reference

Your own site · 80×15
<a href="https://agentmods.dev/skills/fireostendere/mcp_diptrace/diptrace-xml"><img src="https://agentmods.dev/badge/skills/fireostendere/mcp_diptrace/diptrace-xml.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 34 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 420 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.00034 $0.00420
Opus 5 $0.00017 $0.00210
Sonnet 5 $0.00007 $0.00084
Haiku 4.5 $0.00003 $0.00042

Measured 9d ago against content hash 7914238f5326, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

diptrace-xml-reference 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 9d 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.

reference/diptrace-xml/SKILL.md · 28 lines

How it starts

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

DipTrace XML reference

Use this guide when changing the XML parser, compiler, bridge, fixture or review code. Read REFERENCE.md, the clean-room spec_inventory.json, and the measured FORMAT_COVERAGE.md. The inventory is derived from project-owned observations; it is not a redistributed vendor manual.

Required workflow

  1. Identify the XML dialect and exact element/attribute being changed.
  2. Distinguish synthetic observation, controlled export, private/manual evidence and still-open behavior; never promote one class into another by assertion.
  3. Preserve unknown attributes/elements and stable IDs outside the operation boundary.
  4. Add regression coverage and update evidence/trust disclosure for writer/review behavior.
  5. Run relevant parser, geometry, packaging, provenance and MCP-contract checks.
  6. For native compatibility claims, bind the result to an exact DipTrace/editor version and exact candidate/artifact.

Current evidence boundaries

  • Component/@Angle has later manual DipTrace PCB Layout 5.3.0.3 evidence consistent with the radians reader/writer convention and is PASS at the project-manual checkpoint. Broader/public package-owned evidence remains scoped rather than inferred.
  • Internal raw-preserving Component/Pattern Library mutation exists and has controlled real Component Editor / Pattern Editor evidence; public native-library mutation is still unregistered and broader identity/canonicalization semantics remain evidence-gated.
  • Synthetic fixtures do not prove DipTrace 5.3 compatibility.
  • NetClass-aware routing/review behavior remains feature-specific and is not equivalent to complete native DRC.
  • Copper refill, manufacturing, full DSN/SES and other native-host semantics remain exact-scope evidence questions where documented.

Do not claim vendor permission, endorsement, universal DipTrace compatibility or production readiness from this reference or from the inventory.

Read the full file on GitHub · 28 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 9d ago First seen · 28 lines · 34 tokens per session scan A 7914238f5326

Subscribe to this mod's changes

diptrace-xml-reference is a skill published in the GitHub repository fireostendere/mcp_diptrace (22 stars, last pushed 5d ago), licensed Apache-2.0. It adds 34 tokens to every session and 420 once invoked, about $0.0002 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 skills, from other repositories

gke-compute-classes

Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…

google/skills · 83 tokens

jetson-diagnostic

Read-only Jetson health snapshot for identity, memory, GPU, thermal, power, storage, services, and top processes.

NVIDIA/skills · 30 tokens

doca-socket-relay

Use this skill when the operator is driving the DOCA Socket Relay to bridge a socket-oriented host application onto a BlueField DPU peer without rewriting it — picking the deployment shape (in-process, sidecar, or BlueField service container), configuring the host-side socket and the DPU-side forwarding endpoint…

NVIDIA/skills · 236 tokens

offensive-z-wave

Z-Wave attack methodology — sniffing with Z-Force / EZ-Wave / RTL-SDR + ZniffMobile, S0 (legacy) network-key derivation flaw and key reuse, S2 (modern) ECDH commissioning analysis, replay/injection on unauthenticated nodes, default-key brute-force on test deployments, and home-automation hub pivots. Use when targeting…

SnailSploit/Claude-Red · 113 tokens

hsb-flash

Flash the FPGA on an HSB board connected to an NVIDIA devkit. Supports HSB Lattice boards (FPGA versions 2407, 2412, 2507, 2510) and Leopard Imaging VB1940 "all-in-one" cameras (FPGA versions 2507, 2510). Uses release-specific YAML manifests and board-type-specific program commands. Lattice and VB1940 commands must…

NVIDIA/skills · 94 tokens

jetson-validate-image

Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.

NVIDIA/skills · 50 tokens