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 ksachdeva/zephyr-rtos-ai --skill zephyr-kernel-datapassinggit clone --depth 1 https://github.com/ksachdeva/zephyr-rtos-aiWrote 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/ksachdeva/zephyr-rtos-ai/zephyr-kernel-datapassing)<a href="https://agentmods.dev/skills/ksachdeva/zephyr-rtos-ai/zephyr-kernel-datapassing"><img src="https://agentmods.dev/badge/skills/ksachdeva/zephyr-rtos-ai/zephyr-kernel-datapassing/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/ksachdeva/zephyr-rtos-ai/zephyr-kernel-datapassing"><img src="https://agentmods.dev/badge/skills/ksachdeva/zephyr-rtos-ai/zephyr-kernel-datapassing.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.00075 | $0.00689 |
| Opus 5.5 | $0.00030 | $0.00276 |
| Sonnet 5.5 | $0.00015 | $0.00138 |
| Haiku 4.5 | $0.00007 | $0.00069 |
Grade A, and why
zephyr-kernel-datapassing 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 1mo 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Zephyr Kernel Data Passing
Overview
This skill provides expert knowledge on Zephyr kernel objects and subsystems used for data passing. It helps in selecting the right mechanism for the task and provides implementation details.
Workflow
1. Selection Strategy
To choose the correct data passing mechanism, first determine the requirements:
- Participants: Thread-to-Thread? ISR-to-Thread? One-to-Many?
- Data Size: Fixed small structure? Arbitrary size? Byte stream?
- Behavior: FIFO? LIFO? Synchronous? Pub/Sub?
- Coupling: Tight (direct reference) or loose (decoupled)?
Step 1: Read references/comparison.md to see the features, pros, cons, and a decision flowchart.
2. Implementation
Once the mechanism is selected, use the implementation guide to write the code.
Step 2: Read the appropriate reference:
- Kernel Objects: references/data_passing.md for FIFO, LIFO, Stack, Message Queue, Mailbox, Pipe.
- ZBus (Pub/Sub): references/zbus.md for publish-subscribe communication.
- Ring Buffer: references/ring_buffer.md for low-level byte stream buffering.
3. API & Configuration
For API signatures, Kconfig options, and sample locations.
Step 3: Read references/api.md for:
- Complete API function signatures.
- Kconfig options for each mechanism.
- Header file and sample locations.
4. Troubleshooting
If debugging data passing issues, refer to the Common Pitfalls section at the end of references/data_passing.md.
Source Locations
| Description | Path |
|---|---|
| Data Passing Docs | <zephyr-ws-dir>/zephyr/doc/kernel/services/data_passing |
| ZBus Docs | <zephyr-ws-dir>/zephyr/doc/services/zbus/ |
| Kernel Header | <zephyr-ws-dir>/zephyr/include/zephyr/kernel.h |
| ZBus Header | <zephyr-ws-dir>/zephyr/include/zephyr/zbus/zbus.h |
| Ring Buffer Header | <zephyr-ws-dir>/zephyr/include/zephyr/sys/ring_buffer.h |
| MsgQ Sample | <zephyr-ws-dir>/zephyr/samples/kernel/msg_queue |
| ZBus Samples | <zephyr-ws-dir>/zephyr/samples/subsys/zbus/ |
| Philosophers Sample | <zephyr-ws-dir>/zephyr/samples/philosophers |
What ships with it
5 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.
- 1mo ago First seen · 54 lines · 75 tokens per session scan A 086249d5cc57
zephyr-kernel-datapassing is a skill published in the GitHub repository ksachdeva/zephyr-rtos-ai (23 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 75 tokens to every session and 689 once invoked, about $0.0003 per session on Opus 5.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
home-assistant
This skill should be used when helping with Home Assistant setup, including creating automations, modifying dashboards, checking entity states, debugging automations, and managing the smart home configuration. Use this for queries about HA entities, YAML automation/dashboard generation, or troubleshooting HA issues.
raspberry-pi-pico2
Use when developing with Raspberry Pi Pico 2 or the Pi Debug Probe.
piper-tts-training
Train custom TTS voices for Piper (ONNX format) using fine-tuning or from-scratch approaches. Use when creating new synthetic voices, fine-tuning existing Piper checkpoints, preparing audio datasets for TTS training, or deploying voice models to devices like Raspberry Pi or Home Assistant. Covers dataset preparation…
gap
Program robots with GaP (graph-as-policy) — compile natural-language tasks into typed, verified robot skill graphs and run them on simulators or real robots. Use when the user mentions GaP or graph-as-policy, robot manipulation, robot skills, robot tools or capabilities, skill registries, open-robot-skills, LIBERO or…
post-processing
Extract, analyze, and summarize simulation output data — pull spatial fields at specific timesteps, compute time-series trends and detect steady state, extract line profiles through the domain, generate statistical summaries and distributions, calculate derived quantities (gradients, fluxes, volume fractions…
nonlinear-solvers
Select and configure nonlinear solvers for root-finding f(x)=0, optimization min F(x), and least-squares problems — choose among Newton, Newton-Krylov, quasi-Newton (BFGS, L-BFGS), Broyden, Anderson acceleration, and Levenberg-Marquardt methods, configure line search or trust-region globalization, diagnose convergence…