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 wedsamuel1230/arduino-skills --skill field-power-and-connectivity-triagergit clone --depth 1 https://github.com/wedsamuel1230/arduino-skillsWrote 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/wedsamuel1230/arduino-skills/field-power-and-connectivity-triager)<a href="https://agentmods.dev/skills/wedsamuel1230/arduino-skills/field-power-and-connectivity-triager"><img src="https://agentmods.dev/badge/skills/wedsamuel1230/arduino-skills/field-power-and-connectivity-triager/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/wedsamuel1230/arduino-skills/field-power-and-connectivity-triager"><img src="https://agentmods.dev/badge/skills/wedsamuel1230/arduino-skills/field-power-and-connectivity-triager.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.00054 | $0.00727 |
| Opus 5 | $0.00027 | $0.00364 |
| Sonnet 5 | $0.00011 | $0.00145 |
| Haiku 4.5 | $0.00005 | $0.00073 |
Grade A, and why
field-power-and-connectivity-triager 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 12d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Field Power And Connectivity Triager
Use this skill when the project works on the bench but breaks when powered the way it will be used in the real world. Apply it to any board or load whose voltage/current path is uncertain; the ESP32 examples are common cases, not a claim that the same limits apply to every board.
Resources
references/power-path-triage.md- USB vs VIN vs 3V3 diagnosis workflowreferences/wifi-and-peak-current.md- WiFi startup, brownout, and current-peak behaviorreferences/measurement-checklist.md- what to measure before blaming the code../../docs/board-support/uno-r4-family.md- Uno R4 family board caveats where relevant
When to Use
Use this skill when the request includes:
- "works on USB but not on my power supply"
- WiFi connects on the bench but not in deployment
- field-only resets, brownouts, or sensor instability
- suspected regulator or wiring-path weakness
- battery, VIN, or 3V3 supply-path questions
Workflow
- Reproduce the split:
- USB works
- intended power path fails
- Open
references/power-path-triage.mdto classify the supply path. - If WiFi or radio startup is involved, open
references/wifi-and-peak-current.md. - Capture actual measurements from
references/measurement-checklist.mdbefore assuming the failure is in user code. - If the target is Uno R4 WiFi, open
../../docs/board-support/uno-r4-family.mdand keep the connectivity-side hardware split explicit.
Core Rules
- "Works on USB" is evidence about the power path, not proof the code is sound.
- WiFi startup current peaks are first-class suspects on ESP32-class boards.
- Diagnose the supply path before tuning network code blindly.
- Treat sensor instability under field power as a possible power-integrity issue until measurements say otherwise.
- Do not use nominal voltage or an idle current reading as proof of peak-current safety; compare the measured load path with the board and component limits.
Verification
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.
- 12d ago First seen · 76 lines · 54 tokens per session scan A dba817293387
field-power-and-connectivity-triager is a skill published in the GitHub repository wedsamuel1230/arduino-skills (21 stars, last pushed 23d ago), licensed MIT. It adds 54 tokens to every session and 727 once invoked, about $0.0003 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
cardputer-buddy
Iterate on the Cardputer-Adv MicroPython app bundle (Claude Buddy, Snake, Hello) after the device is already provisioned via m5-onboard. Use when the user wants to add a new app, push a single changed .py without re-flashing, watch device serial logs, or run a one-shot REPL command. Trigger on "add an app", "push to…
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…
google-cloud-filestore-autoscale
Inspects Google Cloud Filestore capacity and utilization, evaluates storage scaling rules, and performs capacity autoscaling (scale UP for low free space or scale DOWN for cost optimization). Use when monitoring Filestore instance headroom, resizing instance shares, configuring automated growth/shrink thresholds…
developer-device-platform-basics
Provides guidance and instructions on managing remote devices on Developer Device Platform (DDP). Use when reserving remote Android devices, establishing connection tunnels, checking session status, or extending/cancelling leases. Don't use for iOS or local device/hardware inquiries.
gke-ai-troubleshooting-tpu-dynamic-slices-monitoring
Monitors, troubleshoots, and manages GKE TPU Dynamic Slices custom resources. Use when checking TPU slice lifecycle states, troubleshooting slice provisioning failures, validating single-slice or multi-slice (JobSet) workload manifests, or safely patching stuck finalizers and disabling the slice controller. Don't use…
gke-ai-troubleshooting-tpu-vbar-oom
Diagnoses and prevents vbarcontrolagent segfaults, out-of-memory (OOM) errors, and TPU device initialization failures on TPU v6e nodes in GKE caused by race conditions during TPU device resets or high-frequency metrics polling. Use when troubleshooting vbarcontrolagent crashes, memory cgroup OOMs in serial console…