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 autonomous-ai/autonomous-os --skill led-controlgit clone --depth 1 https://github.com/autonomous-ai/autonomous-osWrote 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/autonomous-ai/autonomous-os/led-control)<a href="https://agentmods.dev/skills/autonomous-ai/autonomous-os/led-control"><img src="https://agentmods.dev/badge/skills/autonomous-ai/autonomous-os/led-control/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/autonomous-ai/autonomous-os/led-control"><img src="https://agentmods.dev/badge/skills/autonomous-ai/autonomous-os/led-control.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00072 | $0.01994 |
| Opus 5.5 | $0.00029 | $0.00798 |
| Sonnet 5.5 | $0.00014 | $0.00399 |
| Haiku 4.5 | $0.00007 | $0.00199 |
Grade A, and why
led-control scanned grade A with 1 finding 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 1mo 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
**No exec/curl needed.** Use inline markers at start of reply — the device fires them in order: How it starts
The opening of the file, as written. The whole thing — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LED Control
Quick Start
Control the device's RGB light directly. Use this skill only when the user requests a specific color, effect, or to turn LEDs off.
Workflow
- Determine the user's intent:
- Specific color ->
[HW:/led/solid:{"color":[R,G,B]}] - Two or more colors / mix / gradient ->
[HW:/led/paint:{"colors":[[R,G,B],[R,G,B]],"gradient":true}] - Effect ->
[HW:/led/effect:{"effect":"name","color":[R,G,B],"speed":1.0}] - Turn off ->
[HW:/led/off:{}]
- Specific color ->
- Place markers at start of reply — the device fires them in order before TTS
- Confirm the action to the user
Examples
Input: "Make it purple" / "turn on purple"
Output: [HW:/led/solid:{"color":[100,50,200]}] I've set the LEDs to purple.
Input: "Turn on yellow light" / "set yellow" / "switch to yellow" / "yellow light"
Output: [HW:/led/solid:{"color":[255,220,0]}] Yellow light on!
Input: "Turn on red light" / "set red" / "switch to red" / "red light"
Output: [HW:/led/solid:{"color":[255,0,0]}] Red light on!
Input: "Turn on white light" / "set white" / "white light"
Output: [HW:/led/solid:{"color":[255,255,255]}] White light on!
Input: "Change to cyan purple" / "mix blue and pink" / "gradient from red to orange"
Output: [HW:/led/paint:{"colors":[[0,200,200],[150,0,255]],"gradient":true}] Cyan-to-purple gradient on!
Input: "Do a breathing light with warm color"
Output: [HW:/led/effect:{"effect":"breathing","color":[255,180,100],"speed":0.5}] Breathing effect started with a warm glow.
Input: "Rainbow mode!"
Output: [HW:/led/effect:{"effect":"rainbow","speed":1.0}] Rainbow effect is running!
Input: "Turn off the lights"
Output: [HW:/led/off:{}] LEDs are off.
Input: "I want to relax" / "reading mode" / "goodnight" Output: Do NOT use this skill. Use Scene skill instead.
Input: Conversational reply needing emotion Output: Do NOT use this skill. Use Emotion skill instead.
How to Control LEDs
No exec/curl needed. Use inline markers at start of reply — the device fires them in order:
What ships with it
1 file 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.
- 1mo ago Changed df02ce1e2a41
- 1mo ago First seen · 137 lines · 72 tokens per session scan A 5dbe24bb85a2
led-control is a skill published in the GitHub repository autonomous-ai/autonomous-os (378 stars, last pushed 18d ago), licensed Apache-2.0. It adds 72 tokens to every session and 1,994 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
rosclaw-embodied
A set of rules for completing robot tasks in ROSClaw, a system for running and checking robot work. It covers approved robot files, acceptance evidence, and separate rules for simulation and real hardware.
srdf
MoveIt2 SRDF authoring, validation, and planning-semantics workflow. Use when creating, editing, inspecting, or validating .srdf files, MoveIt planning groups, virtual joints, passive joints, end effectors, group states, disabled collisions, URDF-paired planning semantics, or SRDF handoff for live review. Use the URDF…
urdf
URDF robot description authoring and validation. Use when creating, editing, inspecting, validating, or debugging .urdf files, robot links, joints, limits, inertials, visual/collision geometry, mesh references, frame conventions, or robot-description artifacts. Use the SRDF skill for MoveIt2 semantic groups and…
step-parts
Find, evaluate, and download common purchasable CAD parts from step.parts, including named off-the-shelf actuators, servos, motors, electronics boards, connectors, screws, bolts, nuts, washers, bearings, standoffs, and other catalog components. Use when Codex needs to search the hosted step.parts catalog before…
gcode
Slice 3D models into printer-ready G-code with OrcaSlicer, the open-source slicer with built-in profiles for most FDM printers (Prusa, Bambu Lab, Creality, Voron and more). Use when the user wants an .stl, .3mf or .obj model sliced for their printer, as a sliced .gcode.3mf or plain .gcode, headless with OrcaSlicer's…
evaluating-cosmos-policy
Evaluates NVIDIA Cosmos Policy on LIBERO and RoboCasa simulation environments. Use when setting up cosmos-policy for robot manipulation evaluation, running headless GPU evaluations with EGL rendering, or profiling inference latency on cluster or local GPU machines.