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 pcb-design-workflowgit 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/pcb-design-workflow)<a href="https://agentmods.dev/skills/fireostendere/mcp_diptrace/pcb-design-workflow"><img src="https://agentmods.dev/badge/skills/fireostendere/mcp_diptrace/pcb-design-workflow/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/pcb-design-workflow"><img src="https://agentmods.dev/badge/skills/fireostendere/mcp_diptrace/pcb-design-workflow.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.00099 | $0.01761 |
| Opus 5.5 | $0.00040 | $0.00704 |
| Sonnet 5.5 | $0.00020 | $0.00352 |
| Haiku 4.5 | $0.00010 | $0.00176 |
Grade A, and why
pcb-design-workflow 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 — 131 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.
PCB design workflow
RAG: engineering memory by default — shared workflow. Carry evidence from MIT/theory, board-design guides and DipTrace courses through architecture, schematic, placement/routing, production and test; consult it at each decision stage.
Coordinate the requested lifecycle stages; read each linked skill only when its stage
is needed. Current user instructions and the project's AGENTS.md, when present,
determine scope, engineering evidence, house rules, and acceptance. A request to prepare a
production package authorizes local preparation, not ordering, payment, or publication.
Establish or resume the project
- Resolve the project directory, schematic/PCB paths, revision, assembly variant, requested endpoint, and available hardware. Reuse the existing naming and reports.
- For an existing design, use
pcb-project-intake to inventory exact
document identities. Read its specification, rules, and
PCB_BUILD.md. - For a new design, create a concise
PROJECT_SPEC.md: purpose, interfaces and pinout, input ranges and protection, rail/load/startup budget, exact critical variants, enclosure/connector datums, dimensions, environment, fab/assembly process, quantity, programming/test access, and measurable acceptance criteria. Record unknowns rather than inventing electrical or mechanical requirements. Ask only about choices that change the design; continue independent work. - Sketch functional blocks and power domains. Bind every consequential requirement to its source and a verification method. Mark estimates and proposed choices explicitly.
- Assemble and maintain the RAG engineering brief from theory, board practice, DipTrace courses and project lessons. Proactively surface coupled risks and alternatives; carry the context from schematic to layout, production and bring-up without waiting for another expert-role prompt. Preserve useful decisions in the existing project journal.
- Before resuming an existing PCB handoff, run the quality gate below. A failure returns work to the owning stage. A new specification without a board is not a passed PCB gate.
What ships with it
2 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.
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 · +5 lines a501aabf6a37
- 1mo ago First seen · 126 lines · 99 tokens per session scan A 00d7fc879860
pcb-design-workflow is a skill published in the GitHub repository fireostendere/mcp_diptrace (24 stars, last pushed 4d ago), licensed Apache-2.0. It adds 99 tokens to every session and 1,761 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.