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 diodeinc/pcb --skill registry-searchgit clone --depth 1 https://github.com/diodeinc/pcbWrote 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/diodeinc/pcb/registry-search)<a href="https://agentmods.dev/skills/diodeinc/pcb/registry-search"><img src="https://agentmods.dev/badge/skills/diodeinc/pcb/registry-search.svg" alt="Measured on agentmods" height="20"></a>- Socket pass
- Snyk pass
- 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.00016 | $0.00444 |
| Opus 5 | $0.00008 | $0.00222 |
| Sonnet 5 | $0.00003 | $0.00089 |
| Haiku 4.5 | $0.00002 | $0.00044 |
Grade A, and why
registry-search 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 2d 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.
What it actually says
Registry Search
Find suitable prepared content before authoring a new reusable package.
Only discover or clone other boards when the user explicitly asks to find or
inspect them; do not search other boards proactively as part of registry
package search. For requested board discovery, use diode_list_boards with
the workspace name. If inspection is requested, git clone the returned HTTPS
URL outside the current checkout; sandbox DiodeHub authentication is already
configured.
| Need | Command |
|---|---|
| Reusable circuit or entrypoint | pcb search -m registry:modules <query> -f json |
| Concrete MPN, footprint, availability, or package behind a symbol | pcb search -m registry:components <query> -f json |
| Candidate public API and source root | pcb doc --package <module-url>@<version> |
Use functional queries for functional needs and MPN/manufacturer queries for named parts. If docs are incomplete, inspect the reported source path or tree; do not infer IO/config names from a search snippet.
Prefer a reusable module or reference circuit that matches the actual need,
then a component with the required support circuitry, or a primitive when only
the raw part is needed. Compare electrical fit, package, pinout, sourcing, and
public API. Use preferred-parts when choosing a concrete MPN. Ask only about
material unresolved tradeoffs.
Instantiate the chosen .zen entrypoint directly in the consuming design.
For example:
PartModule = Module("code.diode.computer/diode/registry/components/<Manufacturer>/<NAME>/<NAME>.zen")
Follow zener-language for dependencies and validation; do not hand-edit
pcb.toml to add the dependency.
If no suitable result exists or a candidate needs a package/API/circuit fix,
use librarian within a registry-authoring task. From board or spec work,
prepare a librarian-dispatch request instead of patching reusable packages
inline.
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.
- 2d ago Changed · -33 lines · -11 tokens per session 38a7cc2db507
- 3d ago Changed · +2 lines 830353229ce8
- 8d ago First seen · 78 lines · 27 tokens per session scan A f0d8b06ae5ef
registry-search is a skill published in the GitHub repository diodeinc/pcb (442 stars, last pushed today), licensed MIT. It adds 16 tokens to every session and 444 once invoked, about $0.0001 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.