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 skills/autonomous-ai/autonomous-os/led-controlnpx 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.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.1 | $0.00072 | $0.02055 |
| Opus 5 | $0.00036 | $0.01027 |
| Sonnet 5 | $0.00014 | $0.00411 |
| Haiku 4.5 | $0.00007 | $0.00205 |
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 6d 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/effect/stop:{}][HW:/led/solid:{"color":[R,G,B]}] - Two or more colors / mix / gradient ->
[HW:/led/effect/stop:{}][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/effect/stop:{}][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/effect/stop:{}][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/effect/stop:{}][HW:/led/solid:{"color":[255,0,0]}] Red light on!
Input: "Turn on white light" / "set white" / "white light"
Output: [HW:/led/effect/stop:{}][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/effect/stop:{}][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.
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.
- 6d 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 (277 stars, last pushed yesterday), licensed Apache-2.0. It adds 72 tokens to every session and 2,055 once invoked, about $0.0004 per session on Opus 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-simforge
Safely install, validate, diagnose, and optimize ROSClaw simulation workflows across MuJoCo/MJWarp, ROS 2 rosbridge, turtlesim, Gazebo, Isaac Sim, Isaac Lab multi-GPU training, MCP, and the signed ROSClaw Hub. Use for evidence-backed physical-AI smoke tests, 4-GPU validation, simulator integration, Hub upload/download…
rosclaw-embodied
Skill "rosclaw-embodied" from ros-claw/rosclaw, covering rosclaw 具身任务纪律, 权威资产, 证据与验收 and 安全分层.
provider-adapter-development
Use for WorldForge provider work: adding adapters, changing capability declarations, promoting scaffolds, debugging provider failures, updating provider catalog docs, or touching LeWorldModel, GR00T, LeRobot, Cosmos-Policy, JEPA, Genie, or JEPA-WMS. Ensures capabilities remain truthful and optional runtimes stay…
optional-runtime-smokes
Use for LeWorldModel, GR00T, LeRobot, PushT robotics showcase, real-checkpoint smoke scripts, checkpoint building, and host-owned optional runtime dependencies. Keeps real-runtime validation explicit without adding heavy ML/robotics packages or artifacts to the base project.
tui-development
Use for the robotics showcase Textual UI: report panes, launch helpers, screenshots, visual tests, and changes under src/worldforge/harness/tui.py or robotics view/rendering modules. Preserves the optional Textual boundary while keeping robotics flow logic testable without the TUI.
rosclaw
Use when operating, validating, or changing ROSClaw physical-AI runtime workflows, especially CLI smoke tests, Practice evidence loops, body/runtime checks, MCP integration, MuJoCo sandbox verification, and safe ROS or hardware boundaries.