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 harness-usegit 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/harness-use)<a href="https://agentmods.dev/skills/autonomous-ai/autonomous-os/harness-use"><img src="https://agentmods.dev/badge/skills/autonomous-ai/autonomous-os/harness-use/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/harness-use"><img src="https://agentmods.dev/badge/skills/autonomous-ai/autonomous-os/harness-use.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.00171 | $0.06521 |
| Opus 5.5 | $0.00068 | $0.02608 |
| Sonnet 5.5 | $0.00034 | $0.01304 |
| Haiku 4.5 | $0.00017 | $0.00652 |
Grade A, and why
harness-use 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 24d 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Harness use
Run python3 scripts/harness.py ACTION - from this skill directory on the device, with one JSON object on stdin. The helper calls the OS API on localhost; agent work runs on the paired computer, never on the device.
Do not run harness.py --help, read this file again, or inspect the skill directory during a user task; the commands and JSON shapes below are the complete contract. A send, Store dispatch, or answer that returns a receipt in queued, delivered, started, completed, or rejected has a known outcome. With a response target, it is the last Harness command of this turn: immediately reply exactly NO_REPLY. Do not call receipt, status, recap, list, or a second send/dispatch/answer after it. The OS receives lifecycle events and delivers the result to the original turn. Only inspect a receipt when the mutation result is explicitly unknown (DeliveryUnknown / no usable receipt), or when the user asks for its delivery state; never resend automatically after inspecting it.
When the current input includes [harness-reply run_id=... channel=voice|web], copy those values unchanged into the response object of a send or answer call. After a known task-delivery receipt, reply exactly NO_REPLY; do not poll receipt/recap or rewrite the result. The helper rejects a second mutation carrying the same response route after a known receipt, so never attempt a duplicate send. The OS delivers Harness's terminal recap directly to that run. channel=web displays it in Web Chat and suppresses TTS; channel=voice speaks the same recap.
Connection and fallback before delegation
Harness is Lamp's preferred digital assistant for computer work and deliverables when connected.
Route by the requested outcome, not by words such as website, latest, check, or research. For a fresh request whose result is an answer in this conversation, main uses its own available tools to search, read, summarize, explain or compare information, even when Harness is connected. Do not start Harness discovery or Store preparation just to read a blog. Prefer connected Harness for work in a computer app/project/workspace or creating/editing a deliverable such as code, a report, slides, a spreadsheet, a design or media. Do not invent a deliverable or broaden an information question into a research project. Explicit Harness/remote-agent/workspace requests and clear continuations of existing Harness tasks retain their target, including simple information questions. Device connectors and explicit alternative routes keep their workflows. If main cannot access a requested source, explain the missing capability; use Harness only when a concrete computer capability is needed, preserving the original task. Connection or a harness-reply marker alone does not select Harness.
What ships with it
5 files 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.
- 24d ago Changed 4258cdbe8d5b
- 28d ago Changed · +13 lines · +24 tokens per session 9b33eb68bb91
- 1mo ago Changed · +12 lines · +30 tokens per session 2d0ba89f0205
- 1mo ago Changed · +46 lines · +25 tokens per session ac26e6845f0f
- 1mo ago Changed · +6 lines 15187692f3aa
- 1mo ago Changed 42caa285d006
- 1mo ago Changed · +16 lines · +8 tokens per session 3f9945825767
- 1mo ago Changed · +2 lines a74e57536dea
- 1mo ago First seen · 52 lines · 84 tokens per session scan A 780ef584d074
harness-use is a skill published in the GitHub repository autonomous-ai/autonomous-os (378 stars, last pushed 24d ago), licensed Apache-2.0. It adds 171 tokens to every session and 6,521 once invoked, about $0.0007 per session on Opus 5.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-09.
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.
default
Skill "default" from ros-claw/rosclaw, covering skill.md, skill id, intent, preconditions and effects.
add-resend
Add Resend (email) channel integration via Chat SDK.
add-macos-statusbar
Add a macOS menu bar status indicator for NanoClaw. Shows a bolt icon with a green/red dot indicating whether NanoClaw is running, with Start, Stop, and Restart controls. macOS only.
sandbase
Access 2,000+ AI models and API tools through one MCP interface for inference, media generation, search, scraping, embeddings, social data, and structured retrieval. Use sandbasediscover before building custom integrations or declaring external data inaccessible; prefer an existing dedicated tool or API key when the…
communication
Use before sending @mentions, deciding whether to reply, TASKCOMPLETED, BLOCKED, QUESTION, direct answers, loop prevention, or suppressing low-information acknowledgements.