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 skills add fireostendere/mcp_diptrace --skill diptrace-revision-reviewgit 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/skills/fireostendere/mcp_diptrace/diptrace-revision-review)<a href="https://agentmods.dev/skills/fireostendere/mcp_diptrace/diptrace-revision-review"><img src="https://agentmods.dev/badge/skills/fireostendere/mcp_diptrace/diptrace-revision-review/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.
<a href="https://agentmods.dev/skills/fireostendere/mcp_diptrace/diptrace-revision-review"><img src="https://agentmods.dev/badge/skills/fireostendere/mcp_diptrace/diptrace-revision-review.svg" alt="Reviewed on agentmods" width="80" 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.00086 | $0.01014 |
| Opus 5.5 | $0.00034 | $0.00406 |
| Sonnet 5.5 | $0.00017 | $0.00203 |
| Haiku 4.5 | $0.00009 | $0.00101 |
Grade A, and why
diptrace-revision-review 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 8d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Read runtime access before selecting tools or declaring a capability unavailable. MCP tools and native/headless CLI are separate interfaces.
DipTrace revision review and ECO
RAG: engineering memory by default — shared workflow. Carry the RAG engineering context across revisions to explain changes, identify coupled consequences, compare alternatives and choose meaningful regression checks.
A comparison is read-only for CAD. An explicit change request permits only that change; it does not authorize overwriting an old release or ordering replacement boards.
Compare exact revisions
- Resolve old/new schematic and PCB paths, BOM variants, release manifests, rules, and relevant firmware versions. Hash each source and preserve immutable baselines. Do not infer the baseline from filenames or modification dates alone.
- Discover MCP capabilities and read models/connectivity for each document with
explicit paths; export binary
.dch/.diprevisions to XML first withdiptrace_mcp.native_xml_exporton private copies. Compare components by stable identity and RefDes, checking manufacturer/MPN, value, fitted/DNP state, pattern, pin numbers, and pin-to-pad map. - Compare nets as endpoint sets: schematic
(sheet, RefDes, pin)and PCB(RefDes, pad). Report renamed nets separately from changed membership. Handle explicit hierarchy/ports, multi-part symbols, and duplicated names; do not conflate an unchanged display name with unchanged connectivity. - Use
compare_schematic_to_pcbfor each matched schematic/PCB revision pair. It compares schematic to PCB, not two arbitrary revisions. For revision diffs, compare exported models with existing repository helpers or ordinary JSON/set operations; never invent a revision-diff MCP tool. - Compare board outline, holes/datums, side/position/orientation, footprints, stackup, netclass/clearance/width constraints, traces/vias, pours/keepouts, testpoints, and silk as applicable. Disclose unmodeled fields and native-format limits. A text XML diff alone is not an electrical or mechanical comparison.
- Recheck source hashes after the read. Identify intended edits, incidental changes, unexplained differences, and evidence gaps with exact affected objects.
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.
- 8d ago Changed · +2 lines 2506dcf57b23
- 1mo ago First seen · 75 lines · 86 tokens per session scan A 887acb8e7d1c
diptrace-revision-review is a skill published in the GitHub repository fireostendere/mcp_diptrace (25 stars, last pushed 4d ago), licensed Apache-2.0. It adds 86 tokens to every session and 1,014 once invoked, about $0.0003 per session on Opus 5.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-09-13.
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…
jetson-diagnostic
Read-only Jetson health snapshot for identity, memory, GPU, thermal, power, storage, services, and top processes.
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…
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…
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…
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.