diptrace-evidence-capture

diptrace-evidence-capture is a skill for Claude Code, Codex from fireostendere/mcp_diptrace. It costs 70 tokens per session (1,358 once invoked), scanned A, original, Apache-2.0.

A workflow for collecting and checking reviewable DipTrace PCB evidence, including board validation, source handling, export capture, and metadata recording.

In plain words
What is it for?
Use it when validating or documenting DipTrace boards through refill, design-rule checks, saving, reopening, XML round trips, or guided evidence capture.
Why use it?
It provides a traceable way to verify board changes and distinguish native DipTrace results from operator-reported actions.

Skill for Claude CodeCodex

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

Good fit Use it when validating or documenting DipTrace boards through refill, design-rule checks, saving, reopening, XML round trips, or guided evidence capture.

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/fireostendere/mcp_diptrace/diptrace-evidence-capture/github.svg)](https://agentmods.dev/skills/fireostendere/mcp_diptrace/diptrace-evidence-capture)
Your own site
<a href="https://agentmods.dev/skills/fireostendere/mcp_diptrace/diptrace-evidence-capture"><img src="https://agentmods.dev/badge/skills/fireostendere/mcp_diptrace/diptrace-evidence-capture/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-evidence-capture

Your own site · 80×15
<a href="https://agentmods.dev/skills/fireostendere/mcp_diptrace/diptrace-evidence-capture"><img src="https://agentmods.dev/badge/skills/fireostendere/mcp_diptrace/diptrace-evidence-capture.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 70 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,358 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00070 $0.01358
Opus 5 $0.00035 $0.00679
Sonnet 5 $0.00014 $0.00272
Haiku 4.5 $0.00007 $0.00136

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

Security

Grade A, and why

diptrace-evidence-capture 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 11d ago.

The scan reads SKILL.md. This mod also ships 2 executable files (scripts/capture_diptrace_evidence.py, scripts/ingest_fixtures.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/diptrace-evidence-capture/SKILL.md · 102 lines

How it starts

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

DipTrace evidence capture

Prefer the most deterministic available evidence path without promoting runtime or operator claims to trusted provenance. For current whole-board PCB validation on a real Windows DipTrace host, use the native headless profile first. For unsupported native actions, editors, format probes, or human visual questions, use the legacy operator workflow in references/operator-workflow.md.

Use public tools/list for exact callable names and get_capabilities for session, document, and feature availability. Native host orchestration is a local helper and does not expand the MCP tool contract.

Native PCB acceptance first

Run the bounded native PCB rail when the task is refill/DRC/save/reopen/XML round-trip evidence:

py -m diptrace_mcp.pcb_native_acceptance run `
  --diptrace-root "C:\Program Files\DipTrace" `
  --project "C:\work\board.dipxml" `
  --output-xml "C:\work\evidence\board.native.dipxml"

For a binary .dip project, provide --baseline-xml expected.dipxml. The helper snapshots the baseline before GUI mutation, runs the real PCB editor on the isolated Win32 desktop by default, invokes the bounded diptrace-5.3-en-v1 menu profile, saves/closes/reopens, exports distinct XML, and writes a *.native-evidence.json sidecar.

Interpret the result exactly:

  • PASS / exit 0: DRC matched a verified success token, structural invariants stayed equal, and the full XML semantic fingerprint equals the immutable baseline.
  • FAIL / exit 1: the native pipeline failed, DRC exposed a positive error count, structural invariants changed, or desktop/window-station/session safety evidence changed.
  • HUMAN_REVIEW_REQUIRED / exit 2: native transport completed but a locale/dialog is unknown, no immutable baseline exists, or a full semantic delta remains after stable structural checks.

Do not reinterpret HUMAN_REVIEW_REQUIRED as PASS. Do not recover from an unknown menu/dialog by coordinate clicks, SendInput, physical cursor movement, or synthesized keyboard shortcuts. A new DipTrace build/locale must first establish a reviewed native profile or fall back to operator capture.

Read the full file on GitHub · 102 lines

Files

What ships with it

3 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. 11d ago First seen · 102 lines · 70 tokens per session scan A cc3da2608170

Subscribe to this mod's changes

diptrace-evidence-capture is a skill published in the GitHub repository fireostendere/mcp_diptrace (22 stars, last pushed yesterday), licensed Apache-2.0. It adds 70 tokens to every session and 1,358 once invoked, about $0.0003 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