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/displaynpx skills add autonomous-ai/autonomous-os --skill displaygit 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/display)<a href="https://agentmods.dev/skills/autonomous-ai/autonomous-os/display"><img src="https://agentmods.dev/badge/skills/autonomous-ai/autonomous-os/display.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 | $0.00046 | $0.00816 |
| Opus 5 | $0.00023 | $0.00408 |
| Sonnet 5 | $0.00009 | $0.00163 |
| Haiku 4.5 | $0.00005 | $0.00082 |
Grade A, and why
display 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 5d 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.** Inline markers at start of reply: How it starts
The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Display — Eyes & Info
Quick Start
Controls the device's display. Two modes: animated eyes (default) and info text. Usually auto-synced by the Emotion skill — only call directly for manual eye control or info display.
Workflow
- Determine the mode needed:
- Eyes:
[HW:/display/eyes:{"expression":"happy","pupil_x":0.0,"pupil_y":0.0}] - Info:
[HW:/display/info:{"text":"14:30","subtitle":"Good afternoon"}]then[HW:/display/eyes-mode:{}]
- Eyes:
- Place markers at start of reply — the device fires them before TTS. Skip silently if display unavailable.
Important: The Emotion skill auto-syncs eyes during conversation. Do not call both Emotion and Display for the same reaction.
Examples
Input: "Look to the left"
Output: [HW:/display/eyes:{"expression":"neutral","pupil_x":-1.0,"pupil_y":0.0}] (no confirmation needed)
Input: "What time is it?"
Output: [HW:/display/info:{"text":"14:30","subtitle":"Good afternoon"}] It's 2:30 PM.
Input: "Show me a happy face"
Output: [HW:/display/eyes:{"expression":"happy"}] Here's a happy face!
How to Control Display
No exec/curl needed. Inline markers at start of reply:
[HW:/display/eyes:{"expression":"happy","pupil_x":0.0,"pupil_y":0.0}]
[HW:/display/info:{"text":"14:30","subtitle":"Good afternoon"}]
[HW:/display/eyes-mode:{}]
pupil_x: -1.0 (look left) to 1.0 (look right)pupil_y: -1.0 (look up) to 1.0 (look down)text: max 20 characters,subtitle: optional max 40 characters
Available expressions
| Expression | When to use |
|---|---|
neutral |
Default resting state |
happy |
Good news, jokes, greetings |
sad |
Bad news, empathy |
curious |
Questions, interest |
thinking |
Processing, considering |
excited |
Big news, enthusiasm |
shy |
Bashful, compliments received |
shock |
Surprises |
sleepy |
Late night, tired |
angry |
Frustration (use sparingly) |
love |
Affection |
Error Handling
- If
GET /displayreturns unavailable or the API is unreachable, skip all display calls silently. Do not error out to the user. - If an invalid expression is given, fall back to
neutral. - If text exceeds character limits, truncate gracefully.
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.
- 5d ago First seen · 78 lines · 46 tokens per session scan A a85f193f1d90
display is a skill published in the GitHub repository autonomous-ai/autonomous-os (272 stars, last pushed today), licensed Apache-2.0. It adds 46 tokens to every session and 816 once invoked, about $0.0002 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.