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 easylogger-integrationgit 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/easylogger-integration)<a href="https://agentmods.dev/skills/easyzoom/aix-skills/easylogger-integration"><img src="https://agentmods.dev/badge/skills/easyzoom/aix-skills/easylogger-integration/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/easyzoom/aix-skills/easylogger-integration"><img src="https://agentmods.dev/badge/skills/easyzoom/aix-skills/easylogger-integration.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.00036 | $0.00747 |
| Opus 5 | $0.00018 | $0.00374 |
| Sonnet 5 | $0.00007 | $0.00149 |
| Haiku 4.5 | $0.00004 | $0.00075 |
Grade A, and why
easylogger-integration 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 11d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
EasyLogger Integration
Overview
Use this skill to integrate EasyLogger without making logs distort the system being debugged. Confirm output backend, timestamp source, concurrency, buffer policy, and log level before relying on logs as evidence.
When To Use
Use this skill when:
- The user wants to add or debug EasyLogger in MCU, RTOS, or bare-metal firmware.
- Logs are missing, truncated, blocking, out of order, too slow, too verbose, or not timestamped correctly.
- The task involves
elog_port, UART output, flash/file logging, filters, colors, async output, or runtime log levels.
Do not use this skill when the issue is raw UART capture quality. Use embedded-serial-log-debug first.
First Questions
Ask for:
- Target MCU/RTOS/compiler and EasyLogger version or source.
- Output backend: UART, RTT, semihosting, file, flash, network, shell, or custom.
- Whether logs can block, allocate memory, or run in interrupt context.
- Timestamp source and desired format.
- Current
elog_cfgand port functions if available. - Symptom and sample log output.
Integration Checklist
-
Bring up one output path. Prove a minimal blocking UART/RTT output works before enabling async, flash, or network logging.
-
Implement port functions deliberately. Output, lock/unlock, time, and optional color handling must match the target environment.
-
Set log levels and filters. Avoid enabling verbose logs globally on timing-sensitive firmware.
-
Decide concurrency policy. Use mutexes or critical sections when multiple tasks or ISRs can log.
-
Bound cost. Understand stack, heap, formatting, blocking time, and output bandwidth.
-
Preserve diagnostic value. Logs should include module, level, time, and enough context to correlate with faults or events.
Porting Checks
elog_port_outputcannot deadlock if called from error paths.- Lock implementation is safe before and after scheduler start.
- ISR logging policy is explicit: forbidden, buffered, or minimal.
- Timestamp source is initialized before first log or handles early boot.
- UART backend does not block forever if host is disconnected.
- Flash/file logging does not erase production data without approval.
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.
- 11d ago First seen · 93 lines · 36 tokens per session scan A 50b9394ff66d
easylogger-integration is a skill published in the GitHub repository easyzoom/aix-skills (31 stars, last pushed 1mo ago), licensed MIT. It adds 36 tokens to every session and 747 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.