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 agodianel/esp32-claude-workbench --skill esp32_log_triagegit clone --depth 1 https://github.com/agodianel/esp32-claude-workbenchWrote 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/agodianel/esp32-claude-workbench/esp32_log_triage)<a href="https://agentmods.dev/skills/agodianel/esp32-claude-workbench/esp32_log_triage"><img src="https://agentmods.dev/badge/skills/agodianel/esp32-claude-workbench/esp32_log_triage/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/agodianel/esp32-claude-workbench/esp32_log_triage"><img src="https://agentmods.dev/badge/skills/agodianel/esp32-claude-workbench/esp32_log_triage.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.00027 | $0.00900 |
| Opus 5 | $0.00014 | $0.00450 |
| Sonnet 5 | $0.00005 | $0.00180 |
| Haiku 4.5 | $0.00003 | $0.00090 |
Grade A, and why
esp32_log_triage 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 13d 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ESP32 Log Triage
Systematically analyze ESP32 serial log output to identify and classify issues.
When to Use
- Debugging unexpected device behavior.
- Analyzing boot failures.
- Reviewing log output after a test run.
- Triaging field-reported issues from log captures.
Steps
1. Identify Log Structure
ESP-IDF log format:
[LEVEL][TAG] (TIMESTAMP) MESSAGE
Levels (severity order):
E— Error (critical failures)W— Warning (potential issues)I— Info (normal operation)D— Debug (detailed tracing)V— Verbose (maximum detail)
2. Extract Critical Events
Search for these high-priority patterns:
Boot Failures
rst:0x1 (POWERON_RESET) → Normal power-on
rst:0x3 (SW_RESET) → Software reset
rst:0x7 (TG0WDT_SYS_RESET) → Task watchdog reset
rst:0x8 (TG1WDT_SYS_RESET) → Interrupt watchdog reset
rst:0xf (BROWNOUT_RESET) → Power supply issue
Crash Signatures
Guru Meditation Error → CPU exception
LoadProhibited → NULL pointer or invalid memory read
StoreProhibited → Write to invalid memory
InstrFetchProhibited → Jump to invalid address
IllegalInstruction → Corrupt code or stack
abort() → Software abort
Stack overflow → Task stack too small
Memory Issues
MALLOC_FAILURE → Heap exhaustion
heap_caps_alloc failed → Specific heap type exhausted
heap corruption detected → Memory corruption
Network Issues
wifi:state: → Wi-Fi state transitions
esp_netif_lwip: Failed → Network interface errors
TRANSPORT_BASE: Failed → Connection failures
MQTT_CLIENT: Error → MQTT protocol errors
3. Classify the Issue
Categorize the primary issue:
| Category | Indicators |
|---|---|
| Boot loop | Repeated reset reasons, never reaches app_main |
| Crash | Guru Meditation, backtrace present |
| Memory | Allocation failures, usage growing over time |
| Watchdog | TG0WDT/TG1WDT reset reasons |
| Network | Connection failures, timeouts, drops |
| Peripheral | I2C/SPI/UART errors, timeout on bus |
| Power | Brownout resets, unstable ADC readings |
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.
- 13d ago First seen · 132 lines · 27 tokens per session scan A 858820c2c2c3
esp32_log_triage is a skill published in the GitHub repository agodianel/esp32-claude-workbench (79 stars, last pushed 5mo ago), licensed MIT. It adds 27 tokens to every session and 900 once invoked, about $0.0001 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
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…
competition-firmware-layout
Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for firmware images, partition tables, boot chains, update packages, extracted filesystems, embedded configs, and device-facing trust boundaries. Use when the user asks to unpack firmware, map partition layout, inspect bootloader or init…
doca-flow
Build and debug DOCA Flow applications on supported NVIDIA NICs/DPUs: define match/action pipes, initialize ports and representors, choose forwarding targets, validate pipes before hardware programming, read counters, match the Flow version to the installed DOCA release, and diagnose Flow API errors. Trigger on DOCA…
diagnose-driver-install
Diagnose NVIDIA driver installation failures on DeepOps-managed nodes — nvidia-smi errors, "No devices were found", DKMS build failures, or GPU pods crash-looping. Use before reinstalling anything.
catc-troubleshoot
Catalyst Center troubleshooting workflows - device unreachable investigation, client connectivity issues, interface down analysis, site-wide outage triage, wireless roaming problems, integration with pyATS for CLI-level diagnostics. Use when a device is unreachable, a user reports connectivity problems, an interface…