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 beriberikix/zephyr-agent-skills --skill kernel-servicesgit clone --depth 1 https://github.com/beriberikix/zephyr-agent-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/beriberikix/zephyr-agent-skills/kernel-services)<a href="https://agentmods.dev/skills/beriberikix/zephyr-agent-skills/kernel-services"><img src="https://agentmods.dev/badge/skills/beriberikix/zephyr-agent-skills/kernel-services.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.00065 | $0.00787 |
| Opus 5 | $0.00032 | $0.00394 |
| Sonnet 5 | $0.00013 | $0.00157 |
| Haiku 4.5 | $0.00006 | $0.00079 |
Grade A, and why
kernel-services 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Zephyr Kernel Services
Move beyond basic threading and logging to build modular, event-driven, and robust Zephyr applications.
Core Workflows
1. Event-Driven Communication (Zbus)
Decouple your modules using a lightweight publish-and-subscribe bus.
- Reference: zbus.md
- Key Tools:
ZBUS_CHAN_DEFINE,ZBUS_SUBSCRIBER_DEFINE,zbus_chan_pub.
2. Behavioral Logic (SMF)
Manage complex system states and transitions using the State Machine Framework.
- Reference: smf.md
- Key Tools:
smf_set_state,SMF_CREATE_STATE, Hierarchical states.
3. Background Processing (Work Queues)
Defer long-running or non-critical tasks to prevent blocking interrupts or high-priority threads.
- Reference: settings_workqueue.md
- Key Tools:
k_work_submit,k_work_delayable, Custom work queues.
4. Persistence (Settings)
Save and restore configuration data and state across reboots.
- Reference: settings_workqueue.md
- Key Tools:
settings_load,settings_save_one, NVS backends.
Quick Start (Zbus)
// Define a channel for sensor data
ZBUS_CHAN_DEFINE(sensor_data_chan, struct sensor_msg, NULL, NULL, ZBUS_OBSERVERS_EMPTY, ZBUS_CHAN_DEFAULTS);
// Publish from a thread
zbus_chan_pub(&sensor_data_chan, &msg, K_NO_WAIT);
Professional Patterns (Asset Tracker Style)
- Modularity: Use Zbus as the backbone for inter-module communication.
- Predictability: Use SMF to define clear lifecycle states for each module (e.g., Uninitialized -> Ready -> Active -> Error).
- Responsiveness: Use custom work queues for sensor data ingestion to keep the main thread responsive for cloud communication.
- Sensor Integration: For sensor data ingestion patterns, see the hardware-io skill.
Automation Tools
- zbus_channel_lint.py: Detect duplicate
ZBUS_CHAN_DEFINEnames across source files.
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 69 lines · 65 tokens per session scan A 7e21fdb36032
kernel-services is a skill published in the GitHub repository beriberikix/zephyr-agent-skills (63 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 65 tokens to every session and 787 once invoked, about $0.0003 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
mobile-hardware-ble-nfc
BLE scanning/connecting/GATT operations with react-native-ble-plx, NFC tag reading/writing with react-native-nfc-manager, permissions, background mode, battery-efficient patterns.
mactop
Retrieve real-time hardware metrics from Apple Silicon Macs using mactop. Provides CPU, RAM, GPU, power, thermal, network, disk I/O, and Thunderbolt bus information. Use when the user wants system stats, hardware monitoring, or performance metrics on Apple Silicon Macs.
home-assistant-integration
Use this skill when creating, scaffolding, reviewing, or maintaining Python Home Assistant custom integrations, including work on customcomponents, manifests, config flows, options flows, config entries, platforms/entities, DataUpdateCoordinator, integration automation triggers, diagnostics, repairs…
home-assistant-card
Use when creating, reviewing, debugging, or maintaining Home Assistant custom Lovelace cards or card editors, including custom elements, Web Components, hass data, setConfig, getCardSize/getGridOptions, getConfigElement/getConfigForm, window.customCards, resource registration, HACS card packages, entity display…
zephyr-i2c
Comprehensive Zephyr I2C subsystem expertise for Inter-Integrated Circuit bus communication. Use when: (1) Configuring I2C controllers or devices via devicetree or Kconfig, (2) Implementing synchronous I2C transfers with i2ctransfer/i2cread/i2cwrite, (3) Using register access helpers like…
zephyr-power-management
Expert guidance on Zephyr RTOS power management. Use when working with system sleep states, runtime device power management, wake sources, PM policy constraints, low-power design, wake-latency tradeoffs, or measuring and debugging current draw in Zephyr applications and drivers.