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-settingsgit 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-settings)<a href="https://agentmods.dev/skills/ksachdeva/zephyr-rtos-ai/zephyr-settings"><img src="https://agentmods.dev/badge/skills/ksachdeva/zephyr-rtos-ai/zephyr-settings/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-settings"><img src="https://agentmods.dev/badge/skills/ksachdeva/zephyr-rtos-ai/zephyr-settings.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.00096 | $0.00826 |
| Opus 5 | $0.00048 | $0.00413 |
| Sonnet 5 | $0.00019 | $0.00165 |
| Haiku 4.5 | $0.00010 | $0.00083 |
Grade A, and why
zephyr-settings 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 9d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Zephyr Settings Skill
Quick Start
- Choose Backend: See references/backend_comparison.md
- Define Handler: Use
SETTINGS_STATIC_HANDLER_DEFINEorsettings_handlerstruct - Initialize: Call
settings_subsys_init()→settings_register()→settings_load() - Save Changes: Use
settings_save_one()orsettings_save()
Core Concepts
- Keys: Hierarchical strings (e.g.,
id/serial,wifi/ssid) - Handlers: Implement
h_set,h_get,h_export,h_commitfor your subtree - Backends: Storage implementations (NVS, ZMS, FCB, File) - as of Zephyr 4.1, NVS and ZMS are recommended for non-filesystem storage
Handler Commit Priority
When multiple handlers depend on each other during initialization, use commit priority (cprio):
- Lower values = Higher priority (executed first during commit)
- Default priority: 0
- Use
settings_register_with_cprio()for dynamic handlers - Use
SETTINGS_STATIC_HANDLER_DEFINE_WITH_CPRIO()for static handlers
Example: A network service that other handlers depend on should have higher priority (lower cprio value).
Handler Function Quick Reference
| Function | Called When | Return Value | Required For |
|---|---|---|---|
h_set |
Loading from storage or runtime_set |
0 on success | Loading values |
h_get |
Runtime get (CONFIG_SETTINGS_RUNTIME=y) |
Length on success | Runtime access |
h_export |
Saving all settings | 0 on success | Persistence |
h_commit |
After all settings loaded | 0 on success | Validation/init |
Multiple Storage Sources
Settings supports loading from multiple sources but saves to a single destination:
- Multiple source backends: Load settings from all registered sources
- Single destination backend: All saves go to one location
Use case: Factory defaults in read-only flash + user overrides in NVS.
References
- Backend Selection: references/backend_comparison.md - Choose the right storage backend
- API Reference: references/api_reference.md - Function signatures and structures
- Examples: references/examples.md - Implementation patterns and integrations
- Troubleshooting: references/troubleshooting.md - Debugging common issues
- Locations: references/locations.md - Source code and documentation paths
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.
- 9d ago First seen · 70 lines · 96 tokens per session scan A b9c4cd597b83
zephyr-settings is a skill published in the GitHub repository ksachdeva/zephyr-rtos-ai (23 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 96 tokens to every session and 826 once invoked, about $0.0005 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.
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…
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…