Borrowing it
Nothing to install: this file belongs to fireostendere/mcp_diptrace. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/fireostendere/mcp_diptrace/main/.agents/skills/diptrace-schematic-style/SKILL.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/skills/fireostendere/mcp_diptrace/diptrace-schematic-style)<a href="https://agentmods.dev/skills/fireostendere/mcp_diptrace/diptrace-schematic-style"><img src="https://agentmods.dev/badge/skills/fireostendere/mcp_diptrace/diptrace-schematic-style/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-schematic-style"><img src="https://agentmods.dev/badge/skills/fireostendere/mcp_diptrace/diptrace-schematic-style.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00049 | $0.01776 |
| Opus 5.5 | $0.00020 | $0.00710 |
| Sonnet 5.5 | $0.00010 | $0.00355 |
| Haiku 4.5 | $0.00005 | $0.00178 |
Grade A, and why
diptrace-schematic-style 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 1mo 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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DipTrace Schematic Style
Apply these house rules while creating, generating, or visually cleaning a DipTrace schematic. Datasheets, electrical safety, ERC/DRC, mechanical limits, and manufacturability take precedence.
Run gated learning builds one sheet at a time
When the user is using a board as a training run for repeatable one-prompt generation:
- Apply the repository Knowledge/RAG policy before searching. Query the
configured engineering RAG only when a material unknown fact is required to
decide the design. Pure visual rearrangement, alignment, spacing, or cleanup
must use the user's instruction and current DipTrace state without
knowledge_search. When retrieval is required, record returned document IDs/sections and distinguish retrieved requirements from model inference. - Freeze the purpose, interfaces, component evidence and acceptance checks of one sheet only. Do not create the next sheet until the current sheet passes its declared structural, electrical, readability and native-roundtrip gates.
- On an explicit clean restart, delete only the resolved schematic targets; preserve PCB artifacts unless the user separately includes them. Never use rejected schematic coordinates, wires or generated netlist XML as inputs to the replacement.
- Keep an append-only engineering journal with the query, retrieved sources, mutations, tool results, failures, exact resume point and artifact hashes. RAG is retrieval memory, not gate authority.
- After a gate passes, ingest the journal update and add only reusable, observed workflow rules to this skill. Keep project-specific MPNs, nets and coordinates in project evidence rather than universal skill instructions.
- When native acceptance is required, start from
create_document_from_seedwith a known DipTrace export so nativeSettings,Simulator, and unknown loader fields survive. A synthetic scaffold that parses in MCP is not proof that DipTrace will open it as a normal project. - Opening schematic XML can show DipTrace's
Shift Originimport dialog even for an unchanged control seed. Automation may confirm it only by exact title plus one enabledOKbutton through a Win32 message; otherwise fail closed. Keep page geometry centered at(0, 0)and do not infer a coordinate defect from this dialog alone. - Respect the MCP per-write object limit. If cleaning a native seed exceeds it, split the cleanup into guarded dry-run/commit operations by container or component. Never raise or bypass the limit for convenience.
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.
- 1mo ago Changed · +55 lines fdeaa0133311
- 1mo ago First seen · 102 lines · 49 tokens per session scan A 7d1d8d79e97e
diptrace-schematic-style is a skill published in the GitHub repository fireostendere/mcp_diptrace (25 stars, last pushed 15d ago), licensed Apache-2.0. It adds 49 tokens to every session and 1,776 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
bdf_font_converter
Convert a Unicode BDF bitmap font in writable storage to the DFN1 format used by the display module.
solidworks-vibecad
A planning guide for turning natural-language mechanical design requests into structured, parameterized SolidWorks plans that can be reviewed before execution.
fluidcad-assembly
Building multi-part models in FluidCAD: assemblies, part files, inserting and mating parts, connectors, exposed geometry, part parameters, sub-assemblies, replicated instances, STEP parts, project units, and assembly export. Use this skill whenever the user wants an assembly, a mechanism, a hinge, a slider, several…
gen-assembly
Generate a PartCAD assembly (an ASSY that composes parts with placement and/or mates) from a description, writing down what it is required to be, generating or reusing the component parts and validating the result with the PartCAD CLI. Use for /pc:gen-assembly or when the user asks to generate or create an assembly…
add-interfaces
Enrich an existing PartCAD part with connection interfaces and ports (mating metadata) so it can be mated to other parts automatically. Use for /pc:add-interfaces or when the user asks to add interfaces, ports, connectors, or mating information to a part, or to make parts snap/connect/assemble together.
gen-part
Generate a PartCAD part from a natural-language description (and optional reference images/requirements) by writing down what it is required to be, authoring a CAD script, and validating it with the PartCAD CLI. Use for /pc:gen-part or when the user asks to generate, create, or model a single mechanical part.