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 agentmods add skills/qte77/claude-code-plugins/auditing-pcb-designnpx skills add qte77/claude-code-plugins --skill auditing-pcb-designgit clone --depth 1 https://github.com/qte77/claude-code-pluginsWhat 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 | $0.00043 | $0.00659 |
| Opus 5 | $0.00022 | $0.00329 |
| Sonnet 5 | $0.00009 | $0.00132 |
| Haiku 4.5 | $0.00004 | $0.00066 |
Grade A, and why
auditing-pcb-design 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
PCB Design Audit
Target: $ARGUMENTS
Run KiCad design rule checks and export manufacturing outputs.
References (MUST READ)
Read these before proceeding:
references/kicad-cli-reference.md— DRC/ERC commands, JSON output schema, gerber/BOM export
Workflow
-
Detect kicad-cli — Verify
kicad-cliis available, report version -
Find project files — Glob for
*.kicad_pro,*.kicad_sch,*.kicad_pcb -
Run ERC on schematic:
kicad-cli sch erc --output erc-report.json --format json <schematic.kicad_sch> -
Run DRC on PCB:
kicad-cli pcb drc --output drc-report.json --format json <pcb.kicad_pcb> -
Parse JSON reports — Categorize violations by severity (error/warning/exclusion)
-
If clean (no errors), export manufacturing outputs:
- Gerbers:
kicad-cli pcb export gerbers --output gerbers/ <pcb.kicad_pcb> - Drill:
kicad-cli pcb export drill --output gerbers/ <pcb.kicad_pcb> - BOM:
kicad-cli sch export bom --output bom.csv <schematic.kicad_sch>
- Gerbers:
-
Generate findings report at
docs/pcb-audit-report.md
Output Format
# PCB Audit Report: <Project Name>
## Tool Version
kicad-cli <version>
## ERC Results
- Errors: N
- Warnings: N
- <violation description> @ <sheet:component>
## DRC Results
- Errors: N
- Warnings: N
- <violation description> @ <coordinates>
## Manufacturing Outputs
- [ ] Gerbers exported to gerbers/
- [ ] Drill files exported to gerbers/
- [ ] BOM exported to bom.csv
## Recommendations
...
Rules
- Never export gerbers if DRC has unresolved errors
- Report all warnings even if they are excluded in KiCad
- Include exact coordinates/references for every DRC/ERC finding
- Do not modify KiCad project files — this is a read-only audit
What ships with it
1 file 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.
- 2d ago First seen · 81 lines · 43 tokens per session scan A d6f9d8211eec
auditing-pcb-design is a skill published in the GitHub repository qte77/claude-code-plugins (2 stars, last pushed 4d ago), licensed Apache-2.0. It adds 43 tokens to every session and 659 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-31.
Other skills, from other repositories
esp32-expert
This skill should be used for ESP32-specific hardware and runtime work in ESP-IDF, Arduino-ESP32, or PlatformIO projects: target/build detection, FreeRTOS tasks and ISRs, memory/DMA, peripherals, power, networking/security, OTA, crash diagnosis, and unattended reliability. Trigger on "debug this ESP32 crash", "review…
esp32-expert
This skill should be used when the user is writing, reviewing, debugging, or architecting C++ firmware for ESP32 and variants (ESP32-S2, S3, C3, C6, H2, P4) using ESP-IDF or PlatformIO. Provides expert critique covering FreeRTOS task design, memory management (IRAM/DRAM/PSRAM), peripheral drivers (I2C/SPI/UART/GPIO)…
orchestrator
FULLY AUTONOMOUS Flutter development pipeline orchestrator. Smart routing: PM analyzes -> creates targeted tasks -> Orchestrator executes only needed agents. Supports Asana task URLs. Includes QE verification via Maestro E2E tests. 7-phase flow: PM -> TodoWrite -> Execute -> Review -> Tests -> QE E2E -> Close.
flutter-guide
Flutter/BLoC Clean Architecture patterns, review checklists, and testing guides. Background knowledge for flutter-dev, flutter-reviewer, flutter-tester. Not user-invocable.
maestro-flutter
Maestro E2E testing knowledge for Flutter apps. YAML-based flows, TestKeys, visual regression, Maestro MCP integration. Background knowledge for QE E2E testing phase.
android-kotlin-compose
Android development with Kotlin and Jetpack Compose. Use when user mentions "Compose", "Jetpack Compose", "Material3", "Hilt", "Room", "ViewModel", or needs to build Android UI, implement MVVM architecture, manage Compose state, or integrate Jetpack libraries (Navigation, Room, Hilt, ViewModel). Triggers on…