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 zephyr-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/zephyr-integration)<a href="https://agentmods.dev/skills/easyzoom/aix-skills/zephyr-integration"><img src="https://agentmods.dev/badge/skills/easyzoom/aix-skills/zephyr-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/zephyr-integration"><img src="https://agentmods.dev/badge/skills/easyzoom/aix-skills/zephyr-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.00044 | $0.00762 |
| Opus 5 | $0.00022 | $0.00381 |
| Sonnet 5 | $0.00009 | $0.00152 |
| Haiku 4.5 | $0.00004 | $0.00076 |
Grade A, and why
zephyr-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 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Zephyr Integration
Overview
Use this skill to debug Zephyr by separating board selection, devicetree, Kconfig, driver binding, and runtime behavior. Zephyr issues usually come from build-time configuration mismatches before they appear as firmware bugs.
When To Use
Use this skill when:
- The user is working with Zephyr RTOS,
west, boards, shields, samples, or custom board ports. - The issue involves devicetree overlays, Kconfig symbols, drivers, threads, logging, flash partitions, networking, Bluetooth, or power management.
- A build succeeds but the device tree binding, generated config, or runtime device readiness is suspicious.
Do not use this skill for generic RTOS scheduling bugs with no Zephyr-specific
surface. Use rtos-debug or freertos-kernel-debug instead.
First Questions
Ask for:
- Zephyr version, SDK/toolchain,
westworkspace layout, board, and sample/app. - Full
west buildcommand,prj.conf, overlays, and board revision. - Relevant devicetree node, binding, compatible string, alias, and chosen node.
- Generated
zephyr.dts,.config, and the failing log or build error. - Whether the issue is build-time, boot-time, driver probing, or runtime.
Debug Workflow
-
Reproduce the build. Capture the exact
west buildcommand, board, app path, and pristine status. -
Inspect generated artifacts. Check
build/zephyr/zephyr.dts,.config, and generated headers before editing source code. -
Prove devicetree binding. Confirm
status = "okay",compatible, pinctrl, clocks, interrupts, aliases, and chosen nodes. -
Prove Kconfig selection. Verify symbols in
.config, dependency chains, and whether another config file overrides the intended value. -
Check device readiness. Use
device_is_ready(), init priority, logging, and driver return codes. -
Debug runtime behavior. Only after configuration is proven, inspect threads, stacks, work queues, interrupts, buffers, and subsystem-specific APIs.
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 · 93 lines · 44 tokens per session scan A b0eec70861ee
zephyr-integration is a skill published in the GitHub repository easyzoom/aix-skills (31 stars, last pushed 1mo ago), licensed MIT. It adds 44 tokens to every session and 762 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-09-03.
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.
audit
Project health audit and health check — architecture, performance, tests, dependencies, code quality. Use when assessing overall project health, before releases, or after refactors.
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.
tidewave-integration
Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.
verify
Verify Elixir/Phoenix changes — compile, format, and test in one loop. Use after implementation, before PRs, or after fixing bugs.