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 easyzoom/aix-skills --skill low-power-debuggit clone --depth 1 https://github.com/easyzoom/aix-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/easyzoom/aix-skills/low-power-debug)<a href="https://agentmods.dev/skills/easyzoom/aix-skills/low-power-debug"><img src="https://agentmods.dev/badge/skills/easyzoom/aix-skills/low-power-debug.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.00033 | $0.00706 |
| Opus 5 | $0.00016 | $0.00353 |
| Sonnet 5 | $0.00007 | $0.00141 |
| Haiku 4.5 | $0.00003 | $0.00071 |
Grade A, and why
low-power-debug 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Low Power Debug
Overview
Use this skill to debug low-power behavior by measuring current and wake sources before changing sleep configuration. Low-power bugs often involve board leakage, clocks, wake flags, debug settings, peripheral state, and firmware sequencing.
When To Use
Use this skill when:
- Current consumption is too high or unexpectedly low.
- The device fails to enter sleep, cannot wake, wakes immediately, or loses debug access.
- The task involves sleep, stop, standby, deep sleep, retention RAM, wake pins, RTC, watchdog, clock gating, or PMIC sequencing.
Do not use this skill when the board cannot boot at all; establish basic boot first.
First Questions
Ask for:
- Chip/board and intended low-power mode.
- Measured current, expected current, and measurement setup.
- Wake sources and whether wake flags are available.
- Debug probe attached or detached during measurement.
- Peripherals left enabled before sleep.
- Power rails, external devices, pull-ups, and board revision.
Workflow
-
Confirm measurement validity. Check meter range, sampling rate, burden voltage, shunt placement, rails included, and whether debugger/USB is attached.
-
Separate firmware from board leakage. Measure baseline board state, external devices, pull-ups, LEDs, regulators, and sensors.
-
Confirm intended sleep mode. Verify the actual mode entered, not just the API called.
-
Capture wake reason. Read wake flags immediately after wake before clearing them.
-
Disable peripherals methodically. Clocks, UART, ADC, timers, DMA, USB, radio, sensors, and pull configurations can dominate current.
-
Protect debug access. Warn that deep sleep may disconnect SWD/JTAG. Use timed wake, GPIO heartbeat, or connect-under-reset recovery.
Checks
- Debugger and semihosting disabled for current measurement.
- Unused GPIO configured to safe states.
- External pull-ups/pull-downs not causing leakage.
- Regulator and sensor quiescent currents accounted for.
- Wake pins polarity and pull state correct.
- RTC/LPTIM/watchdog clock source active if used.
- SRAM/retention domains configured intentionally.
- Interrupt flags cleared before sleep and read after wake.
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 · 95 lines · 33 tokens per session scan A 4137d3b0f0bc
low-power-debug is a skill published in the GitHub repository easyzoom/aix-skills (31 stars, last pushed 1mo ago), licensed MIT. It adds 33 tokens to every session and 706 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
container-home
Answer questions, assist with planning, and help with design decisions for Mick's off-grid shipping container lake home project. Trigger when the user mentions the container home, lake home, Stewart County, LBL, the expansion, solar system, septic permitting, or retirement property.
eide
A build tool for EIDE projects, an embedded-development extension for Visual Studio Code. It finds EIDE project settings and builds firmware using ARM CC or GCC.
audit
Project health audit and health check — architecture, performance, tests, dependencies, code quality. Use when assessing overall project health, before releases, or after refactors.
workflow
A workflow skill for embedded-device projects that plans and runs building, flashing, debugging, observing, and diagnosis tasks.
investigate
Investigate bugs and errors in Elixir/Phoenix — root-cause analysis for crashes, exceptions, stack traces, test failures. Use --parallel for deep 4-track investigation.
narrow-bare-rescue
Narrow bare rescue in Elixir so real errors like KeyError and typos propagate instead of being swallowed. Use to audit rescues and refactor error handling.