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/audionpx skills add autonomous-ai/autonomous-os --skill audiogit 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/audio)<a href="https://agentmods.dev/skills/autonomous-ai/autonomous-os/audio"><img src="https://agentmods.dev/badge/skills/autonomous-ai/autonomous-os/audio.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.00036 | $0.00938 |
| Opus 5 | $0.00018 | $0.00469 |
| Sonnet 5 | $0.00007 | $0.00188 |
| Haiku 4.5 | $0.00004 | $0.00094 |
Grade A, and why
audio 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.
Use `Bash` with `curl` to call the HTTP API at `http://127.0.0.1:5001`. How it starts
The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audio Control
Quick Start
Control the device's speaker and microphone hardware directly. Use this for volume adjustments, test tones, and raw audio recording. This is LOW-LEVEL hardware control only.
Workflow
- Determine the user's audio hardware need:
- Volume adjustment -> use
POST /audio/volume - Check current volume -> use
GET /audio/volume - Diagnostics / test -> use
POST /audio/play-tone - Raw recording -> use
POST /audio/record
- Volume adjustment -> use
- Optionally check device availability first:
GET /audio - Execute the appropriate API call
- Confirm the action to the user
Examples
Input: "Louder please" / "Turn it up"
Output: Check current volume with GET /audio/volume, then increase by ~15 with POST /audio/volume. Confirm: "Volume set to 85%."
Input: "Set volume to 50%"
Output: Call POST /audio/volume with {"volume": 50}. Confirm: "Volume set to 50%."
Input: "Mute" / "Too loud"
Output: Call POST /audio/volume with {"volume": 0}. Confirm: "Muted."
Input: "I can't hear you"
Output: Check current volume with GET /audio/volume, then increase it. Confirm with the new level.
Input: "Say something" / "Tell me a joke" Output: Do NOT use this skill. Just reply normally — your voice pipeline handles TTS automatically.
Tools
Use Bash with curl to call the HTTP API at http://127.0.0.1:5001.
Check audio devices
curl -s http://127.0.0.1:5001/audio
Response:
{
"output_device": 0,
"input_device": 1,
"available": true
}
Set volume
curl -s -X POST http://127.0.0.1:5001/audio/volume \
-H "Content-Type: application/json" \
-d '{"volume": 70}'
Volume range: 0 (mute) to 100 (max).
Get current volume
curl -s http://127.0.0.1:5001/audio/volume
Response: {"control": "Speaker", "volume": 70}
Play test tone
curl -s -X POST "http://127.0.0.1:5001/audio/play-tone?frequency=440&duration_ms=500"
Plays a sine wave. Use for audio testing only. Keep it short (< 1 second).
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 · 102 lines · 36 tokens per session scan A c36fc4990968
audio is a skill published in the GitHub repository autonomous-ai/autonomous-os (272 stars, last pushed yesterday), licensed Apache-2.0. It adds 36 tokens to every session and 938 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 安全分层.
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.
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…
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.