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 klinkdev2026/klayout-klink --skill klayout-gdsfactorygit clone --depth 1 https://github.com/klinkdev2026/klayout-klinkWrote 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/klinkdev2026/klayout-klink/klayout-gdsfactory)<a href="https://agentmods.dev/skills/klinkdev2026/klayout-klink/klayout-gdsfactory"><img src="https://agentmods.dev/badge/skills/klinkdev2026/klayout-klink/klayout-gdsfactory.svg" alt="Measured on agentmods" 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.00045 | $0.01701 |
| Opus 5 | $0.00023 | $0.00851 |
| Sonnet 5 | $0.00009 | $0.00340 |
| Haiku 4.5 | $0.00005 | $0.00170 |
Grade A, and why
klayout-gdsfactory 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 7d 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 — 219 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gdsfactory to KLayout Bridge
gdsfactory generates components with Python. This skill adds the KLayout integration layer through klink's klive-compatible port and structured MCP verification.
Click-to-connect on PDK layouts (use these two tools, nothing manual)
When the user wants ports connected on a foundry-PDK layout (blackbox cells with waveguide stub ports), do NOT orchestrate harvest/pairing/routing yourself. Two MCP tools do the whole job and persist state on disk:
- User marks intent in KLayout: for each connection, they select ONE or TWO klink Port markers (the labeled triangles) and press the SEND toolbar action. Two markers in one SEND = one pair; single-marker SENDs pair up consecutively.
- You call
photonics.connectwithrecent_sends=<number of SENDs>. That is the entire call. It resolves ports exactly from the SEND events, auto-names nets, saves the net table to.klink/specs/, re-harvests ports from live instance positions, routes with gdsfactory, writes polygons, and zooms. Optional style fields:width_um,radius_um,separation_um,route_layer. - After the user MOVES components and asks to redo the wiring, call
photonics.reroutewith just thecellname (addsessionif the layout is not in the primary KLayout window). Connection intent is read from the persisted table — you do not need to remember anything. - If a result has
ok: false, readproblems: each entry states exactly what to do next (usually: tell the user which selection to redo). Never guess pairings yourself.
If port markers are not on screen yet, run port.harvest_blackbox first
(cell + tags map, or let photonics.connect auto-tag) so the user has
markers to click.
Execution Environment
- Run in the SAME interpreter that has klink + gdsfactory.
- KLayout must be running with the klink plugin loaded.
c.show()connects tolocalhost:8082.- Always call
gf.clear_cache()before regenerating a changed component.
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.
- 7d ago First seen · 219 lines · 45 tokens per session scan A fb6b8ccf3982
klayout-gdsfactory is a skill published in the GitHub repository klinkdev2026/klayout-klink (29 stars, last pushed 8d ago), licensed Apache-2.0. It adds 45 tokens to every session and 1,701 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
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.