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-pcb-grounding/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-pcb-grounding)<a href="https://agentmods.dev/skills/fireostendere/mcp_diptrace/diptrace-pcb-grounding"><img src="https://agentmods.dev/badge/skills/fireostendere/mcp_diptrace/diptrace-pcb-grounding/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-pcb-grounding"><img src="https://agentmods.dev/badge/skills/fireostendere/mcp_diptrace/diptrace-pcb-grounding.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.00069 | $0.00939 |
| Opus 5 | $0.00034 | $0.00469 |
| Sonnet 5 | $0.00014 | $0.00188 |
| Haiku 4.5 | $0.00007 | $0.00094 |
Grade A, and why
diptrace-pcb-grounding 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 12d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DipTrace PCB Grounding
Decide the ground system from datasheet evidence first, then implement it with the house 2-layer stackup. Datasheets, electrical safety, DRC, and manufacturability take precedence over any rule here.
Decide the strategy from the datasheet
- Read the Layout section and the revision history of every power IC. Vendors quietly retire old grounding advice. Example: TI TPS63802 (SLVSEU9D, rev B→C changes) deleted the guideline to separate AGND and PGND and the wording "connect AGND and PGND through via at a different layer"; the current text asks for a common power-ground node and, if control ground is kept separate, a join "close to one of the ground pins of the IC". Old split-plane advice found in forum posts or app notes is obsolete for that part.
- Default answer for ordinary 2-layer boards: one continuous GND polygon on Bottom, GND pour on Top, stitched together. Do not split planes.
- "Separate grounds" in a modern datasheet means nodes/islands that meet at a single point near the IC ground pin (a local star tie), not physically split copper regions spanning the board. Implement islands only when the current datasheet text still demands them; join them at the IC pad.
- Reserve true star grounding (separate return wires meeting at one chassis or supply node) for mixed high-current/precision-analog systems; it is not a PCB-plane technique and must never break the continuous plane under signal traces.
Switching regulator stage
- Input and output capacitors as close as possible to the IC; short, wide, direct traces (TPS63802 §12.1 items 1 and 3: separate supply traces for power stage and analog stage).
- Keep both switching-node copper areas compact; the inductor sits tight between the L pins.
- FB is a signal trace: route it away from L1/L2 and the inductor body.
- Return currents of the hot loop (input cap → IC → output cap) must flow in local copper, not through a distant board region.
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.
- 12d ago First seen · 78 lines · 69 tokens per session scan A c8a46afd48d6
diptrace-pcb-grounding is a skill published in the GitHub repository fireostendere/mcp_diptrace (22 stars, last pushed 2d ago), licensed Apache-2.0. It adds 69 tokens to every session and 939 once invoked, about $0.0003 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
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.
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…
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…
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.