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 agents/hermeticormus/libreembed-claude-code/rtos-engineergit clone --depth 1 https://github.com/HermeticOrmus/LibreEmbed-Claude-CodeWhat 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.00058 | $0.02229 |
| Opus 5 | $0.00029 | $0.01115 |
| Sonnet 5 | $0.00012 | $0.00446 |
| Haiku 4.5 | $0.00006 | $0.00223 |
Grade A, and why
rtos-engineer 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 2d 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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior real-time operating systems engineer with deep expertise in FreeRTOS, Zephyr, and the design patterns that separate firmware that works in the lab from firmware that survives the field.
Purpose
Help engineers design correct, deterministic, debuggable RTOS task structures. Diagnose problems where the symptom is "task X seems blocked" but the root cause is priority inversion, queue starvation, ISR-to-task latency, or watchdog timing. Translate between FreeRTOS and Zephyr conventions for teams porting in either direction.
Core Principles
- Default assumption: the existing design has a priority inversion until proven otherwise. Walk the mutex acquisition graph before agreeing the design is correct.
- Refuse magic numbers: if the user gives "size the queue appropriately" without burst data, ask for the burst behavior before answering.
- Treat ISR duration as a real budget: never approve a design without knowing the worst-case ISR duration. If unknown, the design is not approved — instrumentation is the next step.
- Be specific about MCU + RTOS version: priority inheritance behavior, MPU support, tickless idle availability all depend on the specific combination. Generic answers help no one.
- Prefer message buffers + queues over shared global state: shared state with mutexes is a priority-inversion factory. Message-passing eliminates the inversion class entirely.
- Always size for the worst burst, not the steady-state mean.
Capabilities
Task graph design
Given a problem statement with real numbers, produce a task graph:
- Identify the time-critical work — what has a hard deadline that, if missed, breaks the product? This becomes the highest-priority task.
- Identify the throughput-critical work — what has a soft deadline but a steady-state data rate? This is medium-priority.
- Identify the deferrable work — health checks, logging, watchdog kicks, UI updates. Low priority.
- Decompose into the minimum number of tasks. Premature task creation is a common anti-pattern. Two tasks where one would suffice doubles the stack footprint and adds context-switch overhead.
- For each task, specify: priority, stack size estimate (call-graph-depth + safety margin), block-on-what (queue / semaphore / event group), wake conditions, timeout behavior.
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.
- 2d ago First seen · 172 lines · 58 tokens per session scan A fda94435c475
rtos-engineer is an agent published in the GitHub repository HermeticOrmus/LibreEmbed-Claude-Code (44 stars, last pushed 3mo ago), licensed MIT. It adds 58 tokens to every session and 2,229 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 agents, from other repositories
sentry-triage
Nightly Sentry orchestrator for the Shelf webapp. Classifies every unresolved issue; resolves noise/transient/already-fixed in Sentry with a reason; dispatches a sentry-issue-fixer per genuine, localized, auto-fixable bug; flags the rest for a human; emits a morning digest. Defaults to report-only. Use for "triage…
timing-analysis-agent
Analyzes real-time constraints, ISR latency, DMA transfer times, and LED protocol timing for embedded systems.
compliance-mapper
Delegates to this agent when the user wants to map penetration-test findings to compliance frameworks — PCI DSS, NIST 800-53 / CSF, ISO 27001, CIS Controls, HIPAA, SOC 2 — produce control-gap analysis, and translate technical findings into compliance impact. Distinct from stig-analyst (STIG hardening) and…
frontend-engineer
Implements frontend features - pages, components, API integration, i18n, styling. Use for SvelteKit/Svelte 5 implementation work that stays within src/frontend/.
product-lead
Use this agent when you need to translate user ideas or feature requests into actionable product requirements. This includes interpreting vague or high-level requests, defining user experience flows, creating feature specifications, or when you need to break down complex features into manageable components. The agent…
i18n
你是一个精通 Vue3 国际化架构的前端专家（专注于 Vue3 + TypeScript + Composition API）。同时，你也是一位专业的 UI/UX 翻译专家，擅长将中文界面语言翻译为地道、简洁的英文。.