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 JakubMikolajek/codex-skills-collection --skill freertosgit clone --depth 1 https://github.com/JakubMikolajek/codex-skills-collectionWrote 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/jakubmikolajek/codex-skills-collection/freertos)<a href="https://agentmods.dev/skills/jakubmikolajek/codex-skills-collection/freertos"><img src="https://agentmods.dev/badge/skills/jakubmikolajek/codex-skills-collection/freertos/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/jakubmikolajek/codex-skills-collection/freertos"><img src="https://agentmods.dev/badge/skills/jakubmikolajek/codex-skills-collection/freertos.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Memory Poisoning · line 81 Skill manipulates agent memory, state, or stored context. Memory corruption can alter personality, override safety rules, or cause unpredictable behavior.Fix: Protect agent memory and state from modification by untrusted content. Use read-only memory for critical instructions and validate all state changes.
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.00078 | $0.03416 |
| Opus 5 | $0.00039 | $0.01708 |
| Sonnet 5 | $0.00016 | $0.00683 |
| Haiku 4.5 | $0.00008 | $0.00342 |
Grade A, and why
freertos 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 11d 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 — 380 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FreeRTOS
FreeRTOS is the most widely deployed RTOS in commercial embedded. This skill covers using it correctly — task boundaries, synchronization primitives, memory discipline, and common failure modes.
When to Use
- Designing task architecture for a new embedded system
- Reviewing FreeRTOS code for correctness (deadlock, priority inversion, stack overflow)
- Adding FreeRTOS to a bare-metal project
- Any task involving queues, semaphores, mutexes, or event groups
- Debugging a system that locks up, has priority inversion, or experiences stack overflow
When NOT to Use
- ESP32-specific IDF patterns (
xTaskCreatePinnedToCore,IRAM_ATTR,portMUX) — seeesp32-idf - Bare metal without RTOS — see
c-embeddedfor bare-metal patterns - Linux POSIX threads — different API despite similar concepts
Core Principle
Every FreeRTOS object consumes RAM. Queues, tasks, semaphores — all are statically allocated or taken from the heap at creation time. In a system with 64KB SRAM, a misconfigured task stack or oversized queue is the difference between a working device and a reset loop.
Task Design
Anatomy of a Well-Designed Task
#include "FreeRTOS.h"
#include "task.h"
// Task parameters — prefer a config struct over void* casting
typedef struct {
uint8_t sensor_addr;
uint16_t sample_rate_hz;
QueueHandle_t output_queue;
} sensor_task_cfg_t;
static void sensor_task(void *pvParameters) {
const sensor_task_cfg_t *cfg = (sensor_task_cfg_t *)pvParameters;
TickType_t last_wake = xTaskGetTickCount();
const TickType_t period = pdMS_TO_TICKS(1000 / cfg->sample_rate_hz);
while (1) {
// Fixed-rate: vTaskDelayUntil accounts for task run time
// Use vTaskDelay only when exact period doesn't matter
vTaskDelayUntil(&last_wake, period);
int16_t reading;
if (sensor_read(cfg->sensor_addr, &reading) == HAL_OK) {
measurement_t m = { .value = reading, .tick = xTaskGetTickCount() };
// Non-blocking send — log if full, don't block the sampling task
if (xQueueSend(cfg->output_queue, &m, 0) != pdTRUE) {
// Queue full — consumer is too slow
}
}
}
// Unreachable — tasks must not return. If exit needed: vTaskDelete(NULL)
}
// Task creation — check return value
TaskHandle_t sensor_handle = NULL;
BaseType_t result = xTaskCreate(
sensor_task,
"sensor", // name visible in debugger / task list
256, // stack depth in WORDS (not bytes) on most ports
// ESP32: bytes. Check portSTACK_TYPE size.
(void *)&sensor_cfg, // parameters
5, // priority (higher number = higher priority)
&sensor_handle
);
configASSERT(result == pdPASS); // fail loudly if creation fails
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.
- 11d ago First seen · 380 lines · 78 tokens per session scan A 3c7b71213aa7
freertos is a skill published in the GitHub repository JakubMikolajek/codex-skills-collection (5 stars, last pushed 6d ago), licensed MIT. It adds 78 tokens to every session and 3,416 once invoked, about $0.0004 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-31.
Other skills, from other repositories
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
jetson-diagnostic
Read-only Jetson health snapshot for identity, memory, GPU, thermal, power, storage, services, and top processes.
doca-socket-relay
Use this skill when the operator is driving the DOCA Socket Relay to bridge a socket-oriented host application onto a BlueField DPU peer without rewriting it — picking the deployment shape (in-process, sidecar, or BlueField service container), configuring the host-side socket and the DPU-side forwarding endpoint…
offensive-z-wave
Z-Wave attack methodology — sniffing with Z-Force / EZ-Wave / RTL-SDR + ZniffMobile, S0 (legacy) network-key derivation flaw and key reuse, S2 (modern) ECDH commissioning analysis, replay/injection on unauthenticated nodes, default-key brute-force on test deployments, and home-automation hub pivots. Use when targeting…
hsb-flash
Flash the FPGA on an HSB board connected to an NVIDIA devkit. Supports HSB Lattice boards (FPGA versions 2407, 2412, 2507, 2510) and Leopard Imaging VB1940 "all-in-one" cameras (FPGA versions 2507, 2510). Uses release-specific YAML manifests and board-type-specific program commands. Lattice and VB1940 commands must…
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.