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/hermeticormus/libreembed-claude-code/power-mgmt-patternsnpx skills add HermeticOrmus/LibreEmbed-Claude-Code --skill power-mgmt-patternsgit clone --depth 1 https://github.com/HermeticOrmus/LibreEmbed-Claude-CodeWrote 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/hermeticormus/libreembed-claude-code/power-mgmt-patterns)<a href="https://agentmods.dev/skills/hermeticormus/libreembed-claude-code/power-mgmt-patterns"><img src="https://agentmods.dev/badge/skills/hermeticormus/libreembed-claude-code/power-mgmt-patterns.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 | $0.00000 | $0.01532 |
| Opus 5 | $0.00000 | $0.00766 |
| Sonnet 5 | $0.00000 | $0.00306 |
| Haiku 4.5 | $0.00000 | $0.00153 |
Grade A, and why
power-mgmt-patterns 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 5d 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 — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
power-mgmt-patterns
Knowledge Base
Power management patterns for battery-operated embedded systems.
Pattern 1: Sleep Entry Checklist
Before entering Stop/Standby mode, complete these steps in order:
void prepare_for_stop2(void)
{
/* 1. Complete all pending DMA transfers */
HAL_DMA_Abort(&hdma_spi1_tx);
/* 2. Flush UART TX buffer */
while (!LL_USART_IsActiveFlag_TC(USART2)) {}
/* 3. Disable peripheral clocks */
__HAL_RCC_SPI1_CLK_DISABLE();
__HAL_RCC_USART2_CLK_DISABLE();
__HAL_RCC_ADC1_CLK_DISABLE();
/* 4. Configure unused GPIOs as analog (lowest leakage) */
GPIO_InitTypeDef gpio = {
.Mode = GPIO_MODE_ANALOG, .Pull = GPIO_NOPULL,
.Pin = GPIO_PIN_2 | GPIO_PIN_3 /* Unused pins on GPIOB */
};
HAL_GPIO_Init(GPIOB, &gpio);
/* 5. Configure wake-up: EXTI0 (PA0) falling edge */
HAL_EXTI_GetHandle(&hexti0, EXTI_LINE_0);
/* EXTI already configured; just ensure it's enabled */
/* 6. Enter Stop 2 */
HAL_PWREx_EnterSTOP2Mode(PWR_STOPENTRY_WFI);
/* 7. After wake: restore clocks */
SystemClock_Config();
MX_USART2_UART_Init();
MX_SPI1_Init();
}
Pattern 2: RTC Alarm Wake-Up
Wake MCU at a specific time or after an interval using the RTC alarm.
void rtc_set_wakeup_interval(uint32_t seconds)
{
HAL_RTCEx_DeactivateWakeUpTimer(&hrtc);
/* RTCCLK = LSE 32.768kHz, prescaler = 16 → 2048Hz */
/* WUTR reload value = seconds * 2048 */
HAL_RTCEx_SetWakeUpTimer_IT(&hrtc,
seconds * 2048U - 1U,
RTC_WAKEUPCLOCK_RTCCLK_DIV16);
}
void HAL_RTCEx_WakeUpTimerEventCallback(RTC_HandleTypeDef *hrtc)
{
/* Woke from RTC: take sensor reading */
schedule_sensor_read();
}
/* Usage: wake every 60 seconds */
void setup_periodic_wakeup(void)
{
rtc_set_wakeup_interval(60U);
prepare_for_stop2();
}
Pattern 3: GPIO Leakage Prevention
Floating GPIO inputs near the logic threshold (VCC/2) draw up to 1mA per pin.
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.
- 5d ago First seen · 183 lines · 0 tokens per session scan A 4cbe8356d95a
power-mgmt-patterns is a skill published in the GitHub repository HermeticOrmus/LibreEmbed-Claude-Code (44 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,532 tokens. 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
iot-skills
Use when developing with Raspberry Pi Pico (RP2040) for GPIO, I2C, Wi-Fi, MQTT, or sensor integration using MicroPython. Index of 1 skill: KE3036 Keyes Pico learning kit.
hardware-iot-bus
Low-level I2C and SPI bus peripheral control for embedded Linux boards (Orange Pi, Raspberry Pi, RISC-V).
aether-iot-query
Use this skill when the user asks about a live AetherEdge runtime: channels, points, real-time values, history, alarms, rules, models, instances, routing, SHM health, service health, or system status. Use aether CLI commands to answer — do NOT inspect source code, local database files, or config YAMLs to answer…
aether-iot
Build, integrate, diagnose, or generate applications for the AetherEdge AI-native edge kernel. Use for AetherEdge onboarding, SDK compositions, device and topology clients, read-only operations UIs, MCP integration, Domain Packs, or governed IoT commands where live-state authority and physical-device safety must be…
IoT Device Testing
IoT device testing including firmware validation, protocol testing (MQTT, CoAP), power consumption testing, and over-the-air update verification.
iot-expert
Expert-level IoT systems, embedded devices, edge computing, and IoT protocols.