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-spigit 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-spi)<a href="https://agentmods.dev/skills/ksachdeva/zephyr-rtos-ai/zephyr-spi"><img src="https://agentmods.dev/badge/skills/ksachdeva/zephyr-rtos-ai/zephyr-spi/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-spi"><img src="https://agentmods.dev/badge/skills/ksachdeva/zephyr-rtos-ai/zephyr-spi.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.00155 | $0.02758 |
| Opus 5 | $0.00077 | $0.01379 |
| Sonnet 5 | $0.00031 | $0.00552 |
| Haiku 4.5 | $0.00015 | $0.00276 |
Grade A, and why
zephyr-spi 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 10d 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 — 335 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Zephyr SPI
Expert guidance for Zephyr's SPI driver subsystem covering synchronous and asynchronous transfer APIs, devicetree configuration, and common usage patterns.
Table of Contents
- API Selection
- Getting Device Reference
- Common Workflows
- Configuration
- Error Handling
- Troubleshooting
API Selection
Zephyr provides two SPI access methods. Choose based on requirements:
| API | Kconfig | Use Case | Blocking? |
|---|---|---|---|
| Synchronous | (default) | Simple transfers, blocking until complete | Yes |
| Asynchronous | CONFIG_SPI_ASYNC |
Non-blocking, callback/signal on completion | No |
Decision Tree
Simple blocking transfer? → Synchronous (spi_transceive)
Need non-blocking transfer? → Async (spi_transceive_cb / spi_transceive_signal)
High throughput with minimal CPU? → Async with DMA-capable driver
Multiple concurrent SPI operations? → Async with proper buffer management
Getting Device Reference
From Devicetree (Preferred - for SPI Devices)
Use SPI_DT_SPEC_GET to get a complete SPI specification including bus, config, and CS:
#include <zephyr/device.h>
#include <zephyr/drivers/spi.h>
/* Define the SPI device from devicetree */
#define MY_SPI_DEVICE DT_NODELABEL(my_spi_device)
static const struct spi_dt_spec spi_dev = SPI_DT_SPEC_GET(
MY_SPI_DEVICE,
SPI_OP_MODE_MASTER | SPI_WORD_SET(8) | SPI_TRANSFER_MSB
);
/* Runtime check (in main or init) */
if (!spi_is_ready_dt(&spi_dev)) {
printk("SPI device not ready\n");
return -ENODEV;
}
Direct Controller Access (Less Common)
/* Get SPI controller directly */
const struct device *spi = DEVICE_DT_GET(DT_NODELABEL(spi0));
if (!device_is_ready(spi)) {
return -ENODEV;
}
/* Manual config setup */
struct spi_config spi_cfg = {
.frequency = 1000000U, /* 1 MHz */
.operation = SPI_OP_MODE_MASTER | SPI_WORD_SET(8),
.slave = 0,
.cs = {0}, /* No GPIO CS, use hardware CS */
};
What ships with it
4 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.
- 10d ago First seen · 335 lines · 155 tokens per session scan A 8dbabfffb5ef
zephyr-spi is a skill published in the GitHub repository ksachdeva/zephyr-rtos-ai (23 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 155 tokens to every session and 2,758 once invoked, about $0.0008 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
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.
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…
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…
web-components
Architecture and coding rules for single-page applications using web components, BCE layering, lit-html templating, unidirectional Redux-style state management (reduction.js, standards-based), and standards-based client-side routing (Navigation API + URLPattern). Web standards and web platform first, minimal external…
sbce
Spec-driven BCE workflow where one capability spec equals one business component (same name) and the spec is the boundary contract. Invoked as /sbce new|apply (or by intent), it drives declare → converge; the stack's own test loop is the oracle for "done". new accepts a BC name or a natural-language feature…