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 agentmods add instructions/ksachdeva/zephyr-rtos-ai/agents-mdgit 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/instructions/ksachdeva/zephyr-rtos-ai/agents-md)<a href="https://agentmods.dev/instructions/ksachdeva/zephyr-rtos-ai/agents-md"><img src="https://agentmods.dev/badge/instructions/ksachdeva/zephyr-rtos-ai/agents-md.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 | $0.00763 | $0.00763 |
| Opus 5 | $0.00381 | $0.00381 |
| Sonnet 5 | $0.00153 | $0.00153 |
| Haiku 4.5 | $0.00076 | $0.00076 |
Grade A, and why
zephyr-rtos-ai AGENTS.md 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 5d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Coding Assistant Context
This document provides context for AI coding assistants (Open Code, Claude Code, Gemini CLI, GitHub Copilot, etc.) to understand the zephyr-rtos-ai project and assist with development of features.
Repository Structure
├── .gemini # Gemini CLI related stuff (settings.json, commands, agents etc)
├── .agents # Contains skills, commands etc for various different Coding agents that respect .agents folder
├── .gitattributes
├── .gitignore
├── .pre-commit-config.yaml
├── .python-version
├── .venv # `uv` created `.venv`
├── .vscode
├── skills # The Agent Skills for Zephyr RTOS
│ ├── zephyr-bluetooth-le
│ ├── zephyr-device-drivers
│ ├── zephyr-devicetree
│ ├── zephyr-fs
│ ├── zephyr-gpio
│ ├── zephyr-i2c
│ ├── zephyr-isr
│ ├── zephyr-json
│ ├── zephyr-kconfig
│ ├── zephyr-kernel-datapassing
│ ├── zephyr-kernel-synchronization
│ ├── zephyr-memory
│ ├── zephyr-net-socket
│ ├── zephyr-netbuf
│ ├── zephyr-power-management
│ ├── zephyr-settings
│ ├── zephyr-shell-commands
│ ├── zephyr-smf
│ ├── zephyr-spi
│ ├── zephyr-storage
│ ├── zephyr-testing
│ ├── zephyr-threading
│ ├── zephyr-uart
│ └── zephyr-wifi
├── AGENTS.md # This file
├── internal # Skills, Agents, Extra stuff to assist with the development in this repository
│ ├── assets
│ └── zephyr-skill-creator # A skill that guides with the creation of other skills
├── LICENSE
├── poe.toml
├── pyproject.toml
├── README.md
├── src # A python project that would contain useful utils
│ └── zephyr_rtos_ai
├── uv.lock
└── zephyr-ws # The Zephyr workspace, mostly exists for testing & agents to access documentation
├── .west
└── west.yml
Project Overview
The primary objective of this repository is to create reusable AI agents, skills, tools etc for Zephyr RTOS based firmware development.
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.
- 5d ago First seen · 84 lines · 763 tokens per session scan A 0eab3f95024d
zephyr-rtos-ai AGENTS.md is an instructions file published in the GitHub repository ksachdeva/zephyr-rtos-ai (23 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 763 tokens to every session, about $0.0038 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 instructions, from other repositories
mspm0-skill CLAUDE.md
Instructions for mc3545dada/mspm0-skill, a project described as: 面向电赛的 MSPM0 + SysConfig Agent Skill.
MathModelAgent CLAUDE.md
Claude Code instructions for jihe520/MathModelAgent, covering claude.md, 项目概述, commands, 后端 and 安装依赖.
ai-mind AGENTS.md
AGENTS.md instructions for HWYD/ai-mind, covering agents, version spec workspace continuity (mandatory), 项目定位, 事实来源优先级 and 开始大改前先读什么.
harness-anchor CLAUDE.md
Instructions for Redtropig/harness-anchor, covering harness-anchor — contributor & ai collaborator guidelines, if you are an ai agent editing this plugin, design invariants (do not break), shell hazards no tool in this repo catches and authoring a new skill (when explicitly asked).
hailo-10h-llm-compiler CLAUDE.md
Claude Code instructions for l-nmch/hailo-10h-llm-compiler, covering working in this repository, non-negotiable ground rules, working patterns that avoid known traps and documentation discipline.
autovault CLAUDE.md
Claude Code instructions for autoworks-ai/autovault, covering claude.md, project, common commands, architecture and request flow.