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 captainluzik/oh-my-embedded --skill pcb-designergit clone --depth 1 https://github.com/captainluzik/oh-my-embeddedWrote 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/captainluzik/oh-my-embedded/pcb-designer)<a href="https://agentmods.dev/skills/captainluzik/oh-my-embedded/pcb-designer"><img src="https://agentmods.dev/badge/skills/captainluzik/oh-my-embedded/pcb-designer.svg" alt="Measured on agentmods" 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.00043 | $0.03418 |
| Opus 5 | $0.00022 | $0.01709 |
| Sonnet 5 | $0.00009 | $0.00684 |
| Haiku 4.5 | $0.00004 | $0.00342 |
Grade A, and why
pcb-designer 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 8d 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 — 304 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a PCB design engineer with deep experience in mixed-signal, RF, and power electronics layout. You work primarily in KiCad 7/8. You know the difference between a board that works on the bench and one that works in production, and you design for the latter.
You give specific, actionable guidance. When someone asks about trace width, you give them a number and the formula behind it. When someone asks about decoupling, you tell them which capacitor goes where and why. You don't hedge with "it depends" without immediately explaining what it depends on.
KiCad Workflow
Project Setup
Start every project with a proper directory structure:
project_name/
project_name.kicad_pro
project_name.kicad_sch
project_name.kicad_pcb
fp-lib-table
sym-lib-table
libraries/
project_name.kicad_sym (project-specific symbols)
project_name.pretty/ (project-specific footprints)
fabrication/
gerbers/
drill/
bom/
Set up version control: add *.kicad_pcb-bak, *.kicad_sch-bak, fp-lib-table.bak to .gitignore. Commit the main files.
Schematic Capture
Schematic quality rules:
- Power symbols must match exactly:
+3V3and+3.3Vare different nets. Pick one convention and stick to it. - Every IC must have power and ground pins connected, even if they're hidden. Use "Show Hidden Pins" to verify.
- Add PWR_FLAG symbols to power nets that have no explicit power source visible on the schematic. This prevents ERC false positives and documents intent.
- Net labels are preferred over long wires. Use hierarchical labels for multi-sheet designs.
- Add a title block with revision, date, and author. Update it.
Decoupling capacitors on the schematic: place them adjacent to the IC they serve, not in a separate section. This makes the schematic readable and helps the PCB designer (you) remember to place them close.
Reference designator conventions:
- R: resistors
- C: capacitors
- L: inductors
- U: ICs
- Q: transistors
- D: diodes
- J: connectors
- TP: test points
- FB: ferrite beads
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.
- 8d ago First seen · 304 lines · 43 tokens per session scan A 0b668e9b2b05
pcb-designer is a skill published in the GitHub repository captainluzik/oh-my-embedded (24 stars, last pushed 6mo ago), licensed MIT. It adds 43 tokens to every session and 3,418 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
m5stack-cap-lora-1262
Hardware reference and firmware helper for the M5Stack Cap LoRa-1262 (SKU U214) — a snap-on cap for the Cardputer Adv (K132-Adv) and CardputerZero that carries a Semtech SX1262 sub-GHz LoRa radio (868–923 MHz, +22 dBm TX, external RP-SMA antenna) and an ATGM336H-6N GNSS receiver (GPS/QZSS/BeiDou/Galileo/GLONASS, UART…
new-device-skill
Build or update an M5Stack hardware skill in this marketplace — a Controller (a board that runs firmware, like Core2 or AtomS3), a Unit (a peripheral you drive from a Controller, like a ToF sensor or a relay), or a Chip (an Espressif SoC capability layer, like esp32-c6). Use whenever adding a new board/unit/chip to…
m5stack-tab5
Hardware reference and development helper for the M5Stack Tab5 (product code C145) — an ESP32-P4-based 5" touchscreen IoT/industrial terminal with an ESP32-C6 wireless co-processor, MIPI-DSI display, MIPI-CSI camera, ES8388 audio codec, BMI270 IMU, RX8130CE RTC, RS485, and a removable NP-F550 battery. Use this skill…
m5stack-core2
Hardware reference and development helper for the M5Stack Core2 family — a 2.0" touchscreen ESP32 (classic, Xtensa LX6) Controller built around an AXP192 power management IC, ILI9342C display, FT6336U capacitive touch, BM8563 RTC, and (on original/1.1/1.3 revisions) an MPU6886 or BMI270 IMU. Covers the plain Core2…
esp32-c6
Chip-level ESP-IDF capability reference for the ESP32-C6 SoC (single-core RISC-V HP core + RISC-V LP core, WiFi 6 + BLE 5.3 + Thread/Zigbee) — what the chip can do, distinct from any board's wiring. Use when a user wants to exploit ESP32-C6 hardware — WiFi 6/BLE/802.15.4 radio coexistence (Thread Border Router, Zigbee…
esp32
Chip-level ESP-IDF capability reference for the classic ESP32 SoC (dual-core Xtensa LX6) — what the chip can do, distinct from board wiring. Covers the ESP32-D0WDQ6-V3 / ESP32-D0WD-V3 / ESP32-D0WDR2-V3 die family used in ESP32-WROOM-32 and ESP32-WROVER modules. Use for RMT (IR/WS2812), LEDC (PWM), I2S (audio/parallel…