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.01034 |
| Opus 5 | $0.00024 | $0.00517 |
| Sonnet 5 | $0.00010 | $0.00207 |
| Haiku 4.5 | $0.00005 | $0.00103 |
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 10d 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 — 102 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.
Resolve components before placement
For every component, record the result of this exact lookup order before placing or creating it:
- Search installed DipTrace libraries by exact MPN. Reuse the native symbol, pin mapping, and attached pattern.
- If no exact DipTrace match exists, search LCSC/JLCPCB by exact MPN and reuse its catalog/library data.
- Draw a custom component only after both searches have documented zero exact matches; validate its pinout and footprint against the manufacturer datasheet.
Never replace an available exact component with a hand-drawn generic symbol. Apply the same order to connectors and catalog passives.
Place for human reading
- Organize functional flow left-to-right. Put external connectors and other signal or power sources on the left and receiving blocks on the right.
- Put positive rails above the signal path. Use exact installed native power
Net Port symbols for them (for example
+3V3, or a VCC-style symbol whose instance name isVBUS) and native GND symbols below the components they return. Hide a GND name marking when the symbol is already unambiguous and the marking would add rotated clutter. Do not draw long ground wires or use text labels in place of power symbols. - Place each support component beside the IC pin it serves. Move or rotate parts before accepting a long detour, crossing, or ambiguous connection.
- Keep reference designators, values, net names, sheet names, and port labels horizontal, upright, unobstructed, and close to their object. Rotate the part or counter-rotate its markings where necessary.
- Orient or mirror connectors so their wire-facing pins point into the sheet or block while their pin order remains easy to scan from top to bottom.
Wire visibly and locally
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.
- 10d 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 (22 stars, last pushed today), licensed Apache-2.0. It adds 49 tokens to every session and 1,034 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.
Other skills, from other repositories
cad-viewer
Start CAD Viewer and return review links for CAD and robot-description files. Use when visually reviewing .step, .stp, .glb, .stl, .3mf, .dxf, .urdf, .srdf, or .sdf files, especially when handed off from CAD, URDF, SRDF, or SDF generation skills.
solidworks-vibecad
A planning guide for turning natural-language mechanical design requests into structured, parameterized SolidWorks plans that can be reviewed before execution.
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-assembly
Generate a PartCAD assembly (an ASSY that composes parts with placement and/or mates) from a description, 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, mechanism, or multi-part product.
render
Render a PartCAD object or a CAD file to a 2D image - PNG, JPEG, SVG or DXF - from one or many viewing angles (front, back, left, right, top, bottom, iso, or an arbitrary direction), with pc render for an object a package declares or pc adhoc render for a file that belongs to no package. Use for /pc:render or when the…
gen-part
Generate a PartCAD part from a natural-language description (and optional reference images/requirements) by 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.