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 schematic-engineergit 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/schematic-engineer)<a href="https://agentmods.dev/skills/fireostendere/mcp_diptrace/schematic-engineer"><img src="https://agentmods.dev/badge/skills/fireostendere/mcp_diptrace/schematic-engineer/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/schematic-engineer"><img src="https://agentmods.dev/badge/skills/fireostendere/mcp_diptrace/schematic-engineer.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.00096 | $0.03109 |
| Opus 5.5 | $0.00038 | $0.01244 |
| Sonnet 5.5 | $0.00019 | $0.00622 |
| Haiku 4.5 | $0.00010 | $0.00311 |
Grade A, and why
schematic-engineer 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 3d 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 — 224 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.
Schematic Engineer
RAG: engineering memory by default — shared workflow. Use the theory/design corpus for circuit decisions and indexed DipTrace courses for schematic/library workflows; bind both to the actual circuit and its acceptance checks.
Engineer a device from requirements through an editable DipTrace schematic and, only when
scoped, editable PCB. This project adaptation follows the current user instructions and
project AGENTS.md, when present, for RAG, build gates, and media.
Scope and modes
- Identify the user's current mode:
design,schematic,PCB, orreview. - Follow that exact scope. Review and planning are read-only.
- A schematic request does not authorize PCB changes, synchronization, manufacturing output, or release. A PCB request does not imply fab release.
- State the target document paths, requested deliverable, protected documents, and acceptance gates before mutating anything. Ask only about consequential unresolved ambiguity; retain authorization already given in the session.
- Mark gates outside scope as outside scope, not passed. In a machine-checked
PCB_BUILD.md, keep the supported status vocabulary from its handoff template.
Evidence before engineering decisions
- Adopt the default hardware-engineering mode: build and maintain RAG context from circuit theory, practical design guides, DipTrace courses and project lessons without a role prompt. Use it to reason about architecture, alternatives, failure modes and acceptance throughout work.
- Discover the configured knowledge tools before calling them. Inspect the relevant returned documents/sections, not merely a health check. Retrieve part evidence or figures when pinouts, packages, or layout topology require them.
- Use the uploaded courses and guides for methodology and DipTrace practice, and current manufacturer datasheets/errata for exact parts and limits. Use the actual specification and diptrace-datasheet-rules for project rules. Retrieve methodology proactively, including familiar topics and relevant prerequisite material.
- Record source URI/document ID, revision, page/section, applicable constraint, calculation, and resulting decision in the engineering journal. Reuse cited, still-applicable evidence.
- The current user scope overrides stale documentation. Surface technical/safety contradictions and resolve them with authoritative current sources before dependent work.
- If RAG is offline, use verified project evidence or official sources directly. Block only decisions whose required evidence remains unavailable; continue independent work.
- Do not ingest documents into a remote knowledge base unless authorized.
What ships with it
1 file 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.
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.
- 3d ago Changed · +6 lines 05d24d265a97
- 8d ago Changed · +26 tokens per session de7ab73c8e5e
- 1mo ago First seen · 218 lines · 70 tokens per session scan A aac60a07fd1a
schematic-engineer is a skill published in the GitHub repository fireostendere/mcp_diptrace (24 stars, last pushed 4d ago), licensed Apache-2.0. It adds 96 tokens to every session and 3,109 once invoked, about $0.0004 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.