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 easyzoom/aix-skills --skill rt-thread-integrationgit clone --depth 1 https://github.com/easyzoom/aix-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/easyzoom/aix-skills/rt-thread-integration)<a href="https://agentmods.dev/skills/easyzoom/aix-skills/rt-thread-integration"><img src="https://agentmods.dev/badge/skills/easyzoom/aix-skills/rt-thread-integration/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/easyzoom/aix-skills/rt-thread-integration"><img src="https://agentmods.dev/badge/skills/easyzoom/aix-skills/rt-thread-integration.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.00040 | $0.00710 |
| Opus 5 | $0.00020 | $0.00355 |
| Sonnet 5 | $0.00008 | $0.00142 |
| Haiku 4.5 | $0.00004 | $0.00071 |
Grade A, and why
rt-thread-integration 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RT-Thread Integration
Overview
Use this skill to debug RT-Thread by separating BSP configuration, kernel objects, device framework registration, components, and packages. RT-Thread problems often come from missing component config or device registration order.
When To Use
Use this skill when:
- The user is working with RT-Thread, RT-Thread Studio, Env, SCons, BSPs, or packages.
- The issue involves threads, semaphores, mailboxes, message queues, timers, FinSH/MSH, device drivers, DFS, SAL, lwIP, or OTA components.
- A peripheral, filesystem, shell command, or network interface is present in code but missing at runtime.
Do not use this skill for a generic MCU peripheral with no RT-Thread component
surface. Use embedded-peripheral-bringup first. For generic RTOS scheduling
triage, use rtos-debug.
First Questions
Ask for:
- RT-Thread version, BSP, board, toolchain, build system, and
rtconfig.h. - Enabled components/packages from menuconfig or RT-Thread Studio.
- Device name, driver registration path, init level, and FinSH output.
- Thread list, stack sizes, priorities, heap size, and console log.
- Current symptom and the command or API that fails.
Integration Checklist
-
Reproduce the build configuration. Capture BSP, toolchain, package versions,
rtconfig.h, and generated files. -
Prove console and shell. Bring up UART console and FinSH/MSH before deeper component debugging.
-
Check kernel objects. Inspect thread state, stack, priority, tick, heap, and IPC object ownership.
-
Prove device registration. Confirm driver init level, device name, class, open flags, and
list_device. -
Add components one layer at a time. For DFS, SAL, lwIP, USB, or OTA, verify the lower device and config first.
-
Validate package assumptions. Check package versions, include paths, component symbols, and board hooks.
Common Failures
rtconfig.hdoes not include the component the code expects.- Device is registered under a different name than the application opens.
- Driver init runs before clocks, pins, DMA, or heap are ready.
- Thread stack is too small for shell, filesystem, or networking code.
- FinSH command exists but is compiled out by component config.
- Package code assumes a POSIX, DFS, or SAL layer that is not enabled.
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 · 90 lines · 40 tokens per session scan A 9d9298d90e7a
rt-thread-integration is a skill published in the GitHub repository easyzoom/aix-skills (31 stars, last pushed 1mo ago), licensed MIT. It adds 40 tokens to every session and 710 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
container-home
Answer questions, assist with planning, and help with design decisions for Mick's off-grid shipping container lake home project. Trigger when the user mentions the container home, lake home, Stewart County, LBL, the expansion, solar system, septic permitting, or retirement property.
audit
Project health audit and health check — architecture, performance, tests, dependencies, code quality. Use when assessing overall project health, before releases, or after refactors.
investigate
Investigate bugs and errors in Elixir/Phoenix — root-cause analysis for crashes, exceptions, stack traces, test failures. Use --parallel for deep 4-track investigation.
narrow-bare-rescue
Narrow bare rescue in Elixir so real errors like KeyError and typos propagate instead of being swallowed. Use to audit rescues and refactor error handling.
tidewave-integration
Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.
verify
Verify Elixir/Phoenix changes — compile, format, and test in one loop. Use after implementation, before PRs, or after fixing bugs.