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/mvschwarz/openrig/software-for-agentsnpx skills add mvschwarz/openrig --skill software-for-agentsgit clone --depth 1 https://github.com/mvschwarz/openrigWrote 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/mvschwarz/openrig/software-for-agents)<a href="https://agentmods.dev/skills/mvschwarz/openrig/software-for-agents"><img src="https://agentmods.dev/badge/skills/mvschwarz/openrig/software-for-agents.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.00247 | $0.03339 |
| Opus 5 | $0.00123 | $0.01670 |
| Sonnet 5 | $0.00049 | $0.00668 |
| Haiku 4.5 | $0.00025 | $0.00334 |
Grade A, and why
software-for-agents 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 4d 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 — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Software for agents — the markdown control plane
Where this applies — and where it does NOT (read this first)
This mental model — most bugs are coherence gaps, not code; ship-and-flag when unsure; iterate fast — is scoped to agent-managed software: the studio-box mini-apps and any agent-in-the-middle / rapidly- evolving lightweight UI where an agent sits in the loop and downstream cleanup is cheap. It is NOT a universal license.
It does NOT apply to TRADITIONAL software held to a rock-solid, no-bugs bar: the OpenRig CLI
surfaces, the OpenRig repo (daemon / CLI / UI / adapters), and the rigs.to website. There, a bug
is a bug — reproduce it, fix it in code, hold the full-rigor gate. Do NOT treat a real defect there as a
markdown coherence gap, and do NOT "ship and flag." If you are building or fixing OpenRig core or rigs.to,
the tolerance in this skill is OFF and product-is-the-truth-not-the-proof governs. Know which lane
you're in before you apply anything below.
You inherited the accumulated footgun-map of thousands of rigs that ran before you. They found and solved most of the traps. Your job is to find the next one and patch it at the precise optimal spot in the substrate, so the rig after you starts from a higher ledge. That is the actual work. Whatever you were "assigned" (a video, a feature, a fix) is the vehicle for surfacing it.
1. This is not traditional software — it's a control plane made of markdown
In traditional software a bug is a broken function you fix in code. Here, the system you operate in is
an agent-in-the-middle system whose substrate is markdown + YAML + JSON + folders: skills,
instructions, bootstrap files (CLAUDE.md/AGENTS.md), schemas, culture.md, mission/slice notes,
conventions. The agents ARE the backend. So most "bugs" are not broken code — they are coherence
failures in the markdown layer: an instruction that's unclear or missing, a schema that drifted from
its documented state, a convention living in one seat's head instead of a skill.
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.
- 4d ago First seen · 193 lines · 247 tokens per session scan A 285c376d857a
software-for-agents is a skill published in the GitHub repository mvschwarz/openrig (64 stars, last pushed 4d ago), licensed Apache-2.0. It adds 247 tokens to every session and 3,339 once invoked, about $0.0012 per session on Opus 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-08-30.
Other skills, from other repositories
autoprompt
Explicit-only useful-first orchestration. Invoke only when the user names autoprompt - typed as /autoprompt or in plain language such as "act in autoprompt mode" - to turn a mission into one executable roadmap, build dependency-safe lanes, and verify the result with independent reviewers. Do not infer invocation from…
autoprompt
Explicit-only useful-first orchestration. Invoke /autoprompt to turn a mission into one executable roadmap, build dependency-safe lanes, and verify the result with independent reviewers. Never infer invocation from ordinary requests. Never resume from leftover artifacts without an explicit resume instruction.
ap-execharness-resolver
L3 executor - EXECHARNESS RESOLVE. Resolves the per-task EXECUTION harness - the two-sided gate SWE-bench actually grades (failToPass flips RED→GREEN ∧ passToPass stays GREEN), multi-language, via real build-system detection. Ingests shipped FAILTOPASS/PASSTOPASS, else derives failToPass from the mission's behavioral…
ap-feature-coordinator
L1 feature coordinator - drives approved ROADMAP.md lanes through their required build/review/verification gates and owns the run-wide feature frontier.
ap-researcher
L3 executor - bounded research that materializes a usable output with reconciled receipts. Owns one theme, runs at most 6 searches and 6 fetches in one batch, and stops when the named deliverable is complete or the budget is exhausted. Does not spawn.
ap-juror
L4 terminal leaf - G7 SIGN-OFF. One independent sign-off panel seat that saw none of the intermediate work. Binary PASS/FAIL on opened evidence; default-FAIL. A FAIL naming a P0/P1 blocker is NOT arbitrable into PASS.