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 embedded-serial-log-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/embedded-serial-log-debug)<a href="https://agentmods.dev/skills/easyzoom/aix-skills/embedded-serial-log-debug"><img src="https://agentmods.dev/badge/skills/easyzoom/aix-skills/embedded-serial-log-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.00032 | $0.00909 |
| Opus 5 | $0.00016 | $0.00454 |
| Sonnet 5 | $0.00006 | $0.00182 |
| Haiku 4.5 | $0.00003 | $0.00091 |
Grade A, and why
embedded-serial-log-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 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Embedded Serial Log Debug
Overview
Use this skill to make serial logs trustworthy before drawing conclusions from them. Confirm wiring, voltage level, port ownership, baud settings, boot timing, and log source before debugging firmware behavior.
When To Use
Use this skill when:
- The user needs UART boot logs, serial console access, or firmware printf output.
- Serial output is missing, garbled, intermittent, delayed, duplicated, or stops mid-boot.
- The task involves USB-to-UART adapters,
screen,picocom,minicom, logic analyzers, boot logs, or console prompts.
Do not use this skill when the problem is already proven to be a higher-level protocol issue unrelated to raw serial capture.
First Questions
Ask for:
- Board/chip and which UART pins are used.
- USB-to-UART adapter model and voltage level.
- Serial device path, such as
/dev/ttyUSB0or/dev/ttyACM0. - Baud rate, data bits, parity, stop bits, and flow control if known.
- Whether logs are expected from boot ROM, bootloader, kernel, RTOS, or application.
- Whether TX/RX/GND are accessible and common ground is connected.
Workflow
-
Confirm electrical compatibility. Check voltage level, common ground, TX/RX crossing, and whether pins are shared with boot/download modes.
-
Confirm terminal ownership. Ensure no other terminal, programmer, modem manager, or IDE owns the serial port.
-
Start with common settings. Use 115200 8N1 no flow control unless the board documentation says otherwise.
-
Capture from reset. Open the terminal before reset or power-on so early boot logs are not missed.
-
Classify the symptom. Missing output,乱码, only TX visible, only RX visible, stops after bootloader, login prompt only, or application printf missing.
-
Verify with a second observation method. Use a logic analyzer, oscilloscope, known-good adapter, or loopback test when serial output is suspect.
Command Patterns
picocom -b 115200 /dev/ttyUSB0
screen /dev/ttyUSB0 115200
minicom -D /dev/ttyUSB0 -b 115200
stty -F /dev/ttyUSB0 115200 cs8 -cstopb -parenb -ixon -ixoff
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 · 111 lines · 32 tokens per session scan A 32f2233cec50
embedded-serial-log-debug is a skill published in the GitHub repository easyzoom/aix-skills (31 stars, last pushed 1mo ago), licensed MIT. It adds 32 tokens to every session and 909 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.