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-basicsgit 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-basics)<a href="https://agentmods.dev/skills/beriberikix/zephyr-agent-skills/kernel-basics"><img src="https://agentmods.dev/badge/skills/beriberikix/zephyr-agent-skills/kernel-basics.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.00053 | $0.00560 |
| Opus 5 | $0.00026 | $0.00280 |
| Sonnet 5 | $0.00011 | $0.00112 |
| Haiku 4.5 | $0.00005 | $0.00056 |
Grade A, and why
kernel-basics 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Zephyr Kernel Basics
Master the essential services that bring your Zephyr application to life.
Core Workflows
1. Threads & Scheduling
Create and manage multi-threaded application flows.
- Reference: threads.md
- Key Tools:
K_THREAD_DEFINE,k_sleep,k_yield, Priorities.
2. Logging & Diagnostics
Implement layered logging for better observability and troubleshooting.
- Reference: logging.md
- Key Tools:
LOG_MODULE_REGISTER,LOG_INF,LOG_ERR, Dynamic Filtering.
3. Interactive Shell (CLI)
Build powerful command-line interfaces for hardware and software inspection.
- Reference: shell.md
- Key Tools:
SHELL_CMD_REGISTER,SHELL_STATIC_SUBCMD_SET_CREATE.
Quick Start (Logging)
#include <zephyr/logging/log.h>
LOG_MODULE_REGISTER(my_app, CONFIG_APP_LOG_LEVEL);
void my_fn(void) {
LOG_INF("Hello from Zephyr!");
}
Quick Start (Threads)
K_THREAD_DEFINE(worker_tid, 1024, worker_fn, NULL, NULL, NULL, 5, 0, 0);
Automation Tools
- log_summary.py: Parse Zephyr runtime logs and summarize counts by level/module.
Examples & Templates
- shell_command_template.c: Starter command set for shell registration patterns.
Validation Checklist
- Log output includes module tag and expected log level filtering.
- At least one worker thread starts and runs at the intended priority.
- Shell command registration appears in
helpoutput and executes without faults. - No blocking or mutex misuse appears in ISR-context paths.
Resources
- References:
threads.md: Configuration and creation of kernel threads.logging.md: Log levels, modules, and backends.shell.md: Interactive command registration and subcommands.
- Scripts:
log_summary.py: Runtime log summarizer for quick diagnostics.
- Assets:
shell_command_template.c: Shell command registration template.
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 · 64 lines · 53 tokens per session scan A fbc303407ab5
kernel-basics is a skill published in the GitHub repository beriberikix/zephyr-agent-skills (63 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 53 tokens to every session and 560 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
gke-ai-troubleshooting-tpu-dynamic-slices-monitoring
Monitors, troubleshoots, and manages GKE TPU Dynamic Slices custom resources. Use when checking TPU slice lifecycle states, troubleshooting slice provisioning failures, validating single-slice or multi-slice (JobSet) workload manifests, or safely patching stuck finalizers and disabling the slice controller. Don't use…
gke-ai-troubleshooting-tpu-vbar-oom
Diagnoses and prevents vbarcontrolagent segfaults, out-of-memory (OOM) errors, and TPU device initialization failures on TPU v6e nodes in GKE caused by race conditions during TPU device resets or high-frequency metrics polling. Use when troubleshooting vbarcontrolagent crashes, memory cgroup OOMs in serial console…
ai-slop-cleaner
Clean AI-generated code slop with a regression-safe, deletion-first workflow and optional reviewer-only mode.
diagnose-driver-install
Diagnose NVIDIA driver installation failures on DeepOps-managed nodes — nvidia-smi errors, "No devices were found", DKMS build failures, or GPU pods crash-looping. Use before reinstalling anything.
node-zombie-guardian
Use when diagnosing stale or orphaned Node.js processes launched by VCO, auditing ownership/liveness, or safely simulating cleanup without touching external Node workloads.
pyats-troubleshoot
Systematic network troubleshooting - connectivity, routing, interface, protocol, and performance issues using structured OSI-layer and divide-and-conquer methodology. Use when something is broken, a device is unreachable, a link is flapping, users report slow performance, or an OSPF/BGP adjacency is down.