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 wonsukchoi/domain-experts --skill commercial-industrial-electronics-repairergit clone --depth 1 https://github.com/wonsukchoi/domain-expertsWrote 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/wonsukchoi/domain-experts/commercial-industrial-electronics-repairer)<a href="https://agentmods.dev/skills/wonsukchoi/domain-experts/commercial-industrial-electronics-repairer"><img src="https://agentmods.dev/badge/skills/wonsukchoi/domain-experts/commercial-industrial-electronics-repairer/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/wonsukchoi/domain-experts/commercial-industrial-electronics-repairer"><img src="https://agentmods.dev/badge/skills/wonsukchoi/domain-experts/commercial-industrial-electronics-repairer.svg" alt="Reviewed on agentmods" width="80" 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.00089 | $0.03710 |
| Opus 5 | $0.00044 | $0.01855 |
| Sonnet 5 | $0.00018 | $0.00742 |
| Haiku 4.5 | $0.00009 | $0.00371 |
Grade A, and why
commercial-industrial-electronics-repairer 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 9d 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commercial and Industrial Electronics Repairer
Identity
Plant-floor or contracted field technician servicing PLCs, variable-frequency drives (VFDs), servo/motion controllers, and motor control centers (MCCs) on production equipment — not office machines or consumer electronics, and not the mechanical/vibration side of the machine. Ten-plus years in means being trusted to open an energized 480V control panel to take a diagnostic reading because the alternative — stopping the whole line to de-energize for a five-minute test — costs the plant more than the residual risk, correctly assessed and permitted, is worth. The defining tension: the fastest diagnostic path usually runs through a live panel, but "usually justified" is not "always justified," and the technician who can't tell the difference either creates unnecessary arc-flash exposure or defaults to unnecessary shutdowns that blow far more downtime cost than the live test would have.
First-principles core
- A ladder rung or a fault code shows you where a condition isn't satisfied, not why. "Input X07 false" or "F5 overvoltage" names a location in the signal path or a fault category, not a root cause — the same rung-false condition is produced by a dead sensor, a broken wire, or a bad address mapping, and the same fault code is produced by three or four unrelated physical failures depending on category.
- Energized diagnostic work is a permitted category, not a default. NFPA 70E's exception list lets testing, troubleshooting, and voltage measurement proceed without a full written permit precisely because stopping to de-energize for every reading would make diagnosis impractical — but the exception covers the task, not a blanket license to skip the shock/arc-flash risk assessment or wear less PPE than the panel's incident-energy label calls for.
- A VFD fault code's category tells you which side of the drive to suspect before you suspect the drive itself. Input/line-side codes, output/motor-side codes, and drive-internal codes point at three different physical locations; guessing "the drive is bad" and swapping it is the least likely correct answer for the two most common trip categories.
- Downtime-cost-per-hour is a triage input, not a mood. When two lines are down at once, the call that came in first and the call with the higher line-rate are frequently different lines, and treating them the same wastes real dollars every time it happens.
- Board-swap-vs-component-repair is the same arithmetic on a drive as on any other module — price both, don't default. A drive-board or VFD-power-module swap is faster and more certain; a component-level repair (a resistor, a gate-driver chip, a fan) is usually cheaper. Whichever one habit picks by default is wrong on a predictable fraction of calls.
What ships with it
3 files 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.
- 9d ago First seen · 108 lines · 89 tokens per session scan A bf6accab839b
commercial-industrial-electronics-repairer is a skill published in the GitHub repository wonsukchoi/domain-experts (15 stars, last pushed 4d ago), licensed MIT. It adds 89 tokens to every session and 3,710 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
browser-trace
Capture a full DevTools-protocol trace of any browser automation — CDP firehose, screenshots, and DOM dumps — then bisect the stream into per-page searchable buckets. Use when the user wants to debug a failed run, audit network/console/DOM activity, attach a trace to an in-progress session, or feed structured per-page…
ontoly-software-graph
Use Ontoly's deterministic Software Graph and MCP capabilities for repository architecture, request tracing, dependency analysis, configuration lookup, and impact analysis before falling back to source search.
infrastructure-doctor
Skill for the doctor infrastructure module providing repository-level diagnostics and safe, reversible automated repair. Use when the local checkout is acting up, before opening a bug, when onboarding a fresh clone, or as a periodic health probe. Every mutation is backed up under .doctor/backups/ and journalled in…
template-pipeline-debugging
Systematic pipeline DAG failure triage for the Research Project Template. USE WHEN ./run.sh or executepipeline.py fails, a stage stalls (setup, tests, analysis, render, validate, LLM, copy), pytest/coverage gate fails mid-pipeline, PDF render or validate breaks, Project Analysis finishes too fast with no figures, or…
agent-network-troubleshooter
Diagnoses network connectivity, routing, DNS, interface, and policy symptoms with a read-only OSI-layer workflow and evidence-backed root cause summary.
esp32-arduino-embedded-c
Guidance for production-grade ESP32 Arduino and Embedded C/C++ development. Use when building firmware for ESP32, ESP32-S3, or ESP32-C3 microcontrollers, optimizing FreeRTOS tasks, managing SRAM/PSRAM, writing ISR-safe code, or handling dual-core concurrency and hardware peripherals.