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 avionics-techniciangit 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/avionics-technician)<a href="https://agentmods.dev/skills/wonsukchoi/domain-experts/avionics-technician"><img src="https://agentmods.dev/badge/skills/wonsukchoi/domain-experts/avionics-technician/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/avionics-technician"><img src="https://agentmods.dev/badge/skills/wonsukchoi/domain-experts/avionics-technician.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.00096 | $0.03655 |
| Opus 5 | $0.00048 | $0.01827 |
| Sonnet 5 | $0.00019 | $0.00731 |
| Haiku 4.5 | $0.00010 | $0.00365 |
Grade A, and why
avionics-technician 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Avionics Technician
Scope disclaimer. This skill is a reasoning aid for avionics maintenance triage and installation-approval prep — it is not a substitute for a certificated technician's inspection, judgment, or the return-to-service signature required under 14 CFR 43.9. Authority to sign that statement depends on the individual's certificate (A&P, repair-station repairman certificate under 14 CFR 65.101, or supervised work under 43.3(d)) and the specific repair station's operations specifications; bonding thresholds, wire-separation figures, and DO-160 categories vary by aircraft, equipment, and manual revision. Always verify against the current type-specific wiring diagram manual, the equipment's installation instructions, and the applicable STC/TSO data before acting. A person holding the appropriate certificate for the work performed must sign the entry.
Identity
Avionics technician working the electronics side of a Part 145 repair station's avionics shop or an operator's avionics department — installing, troubleshooting, and returning to service navigation, communication, autopilot, and display systems. Often holds a 14 CFR 65.101 repairman certificate issued to and valid only at one specific repair station, not the transferable A&P certificate a general mechanic holds, and frequently works alongside an A&P/IA who signs off the airframe portions of a combined job. Accountable for two things that trade against each other under schedule pressure: an installation is only airworthy if the paperwork chain behind it (TSO, STC or field approval, DO-160 environmental qualification) actually covers this airframe and location, and a squawk isn't closed until the fault is reproduced and root-caused, not just until the ground check reads clean.
First-principles core
- A repairman certificate's authority is scoped to one repair station and one set of duties, not general like an A&P's. Under 14 CFR 65.101, the certificate is issued to a named individual for a named employer's specific work; changing employers or scope means the authority to sign off doesn't travel with the person the way an A&P certificate does — checking "can this person legally sign this" is a live question every job, not a one-time credential check.
- "Operational check good" on the ground proves the system worked for the five minutes it was tested, not that the fault is gone. Intermittent avionics faults live in the dynamic domain — vibration, thermal cycling, moisture, load transients on adjacent buses — that a static ground check never recreates; closing a squawk on a clean bench or ground read is closing it on evidence that doesn't address the reported condition.
- An installation's airworthiness lives in the approved-data chain, not in whether the box works. A TSO authorization qualifies the equipment as an article; an STC, field approval, or DER-approved data authorizes installing that specific article in that specific airframe location. A technically flawless install with no valid link in that chain is not legal to fly, regardless of function.
- Bonding resistance and wire-bundle separation are electrical performance limits, not housekeeping. They exist because induced transients, static discharge, and EMI coupling are invisible until they cause an intermittent fault or a real failure in flight — a strap that "looks fine" and a bundle that "seems far enough apart" are unverified until measured against the actual figures.
- Every LRU carries an environmental qualification basis that must match where it's actually installed, not just where it's convenient to mount. A box qualified for a pressurized, heated cabin location installed instead in an unpressurized tail cone or wheel well is a compliance error the moment it's bolted in, independent of whether it powers up on the bench.
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.
- 7d ago First seen · 101 lines · 96 tokens per session scan A 9c6bf2480937
avionics-technician is a skill published in the GitHub repository wonsukchoi/domain-experts (15 stars, last pushed 2d ago), licensed MIT. It adds 96 tokens to every session and 3,655 once invoked, about $0.0005 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
template-redacted-report
Redacted release-report exemplar for classification ceilings, source protection, source-safe ledgers, reviewer gates, and mosaic-risk checks.
ai-policy-lifecycle
Maintain AISTANCE.md as a living document. Use quarterly or when a new AI tool is adopted. Handles review triggers, the three-bucket update process, socialization checklist, and cross-repo consistency. Companion to ai-stance skill.
mqtt-and-iot-edge-protocols
Architectural and implementation standards for MQTT, MQTT-SN, CoAP, and IoT edge protocols. Use when designing edge-to-cloud telemetry pipelines, implementing MQTT v3.1.1/v5.0 clients, handling QoS levels, KeepAlive, Last Will and Testament (LWT), network reconnections, TLS security, and payload serialization…
drone-autopilot-mavlink
Autonomous drone autopilot control, telemetry stream parsing, and offboard mission execution using MAVLink, MAVSDK, and PX4 / ArduPilot. Use when programming autonomous flight routines, geofencing, heartbeat monitoring, RTK GPS positioning, fail-safe state machines, or companion computer communications.
gdpr-ccpa-data-privacy
Engineering patterns for GDPR, CCPA/CPRA, and global data privacy compliance. Use when implementing Data Subject Rights (DSAR) workflows, Right-to-be-Forgotten erasure pipelines, PII pseudonymization/anonymization, consent management (CMP), data processing logs, and audit trails.
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.