Agent skill

Agent Operated Software

by mvschwarz in mvschwarz/openrig

A skill your agent uses when designing, building, operating, or diagnosing an ongoing application whose live backend or control loop includes OpenRig agents, including applications with a Markdown…

Apache-2.0Auto-check passedAgent Workflows

Install Agent Operated Software

skills CLI
$ npx skills add mvschwarz/openrig --skill agent-operated-software -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mvschwarz/openrig agent-operated-software --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mvschwarz/openrig.git skills-src && mkdir -p .claude/skills && cp -r skills-src/packages/daemon/assets/plugins/openrig-core/skills/agent-operated-software .claude/skills/agent-operated-software && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
agent-operated-software
GitHub stars
6.2k
Token cost
~1.3k tokens
SKILL.md length
692 words
Files
1
Skills in repo
49
Repo updated
First seen
Licence
Apache-2.0

At a glance

A skill your agent uses when designing, building, operating, or diagnosing an ongoing application whose live backend or control loop includes OpenRig agents, including applications with a Markdown…

  • Works in 4 steps: Write to a partial path, never the final… → Verify the property that can actually be… → Flush and atomically rename the partial… → …
  • Diagnosing an ongoing application whose live backend
  • SKILL.md covers Start with the shared taxonomy, Agents are part of the backend, Markdown is the control plane and Make artifacts self-certifying, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Agent Operated Software is an agent skill from mvschwarz/openrig. Use when designing, building, operating, or diagnosing an ongoing application whose live backend or control loop includes OpenRig agents, including applications with a Markdown, YAML, or JSON agent control plane or a thin surface over specialist agent roles.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows, covering Multi-agent orchestration and Markdown. The repository describes itself as: Build your own network of agents from Claude Code, Codex and Pi: persistent teams with roles, shared context and owned work. The licence is Apache-2.0.

When your agent uses it

  • Diagnosing an ongoing application whose live backend
  • Control loop includes OpenRig agents
  • Including applications with a Markdown
  • JSON agent control plane

Example prompts

  • “/agent-operated-software”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Write to a partial path, never the final path.
  2. Verify the property that can actually be wrong, such as duration, streams, resolution, or schema.
  3. Flush and atomically rename the partial artifact to its final path.
  4. Write the manifest, then a .done sentinel last.

What it can do on your machine

Read from SKILL.md and the folder at commit a29dfbc. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Agent Operated Software loads about 1.3k tokens when it runs. Until then it costs about 71 tokens; SKILL.md has 692 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~71
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from mvschwarz/openrig at commit a29dfbc, republished under its Apache-2.0 licence (© mvschwarz). 692 words, ~1,291 tokens.

Download SKILL.mdSave it as .claude/skills/agent-operated-software/SKILL.md (or your agent's skills folder).
name
agent-operated-software
description
Use when designing, building, operating, or diagnosing an ongoing application whose live backend or control loop includes OpenRig agents, including applications with a Markdown, YAML, or JSON agent control plane or a thin surface over specialist agent roles.

Agent-Operated Software

Agent-Operated Software is an ongoing application whose functioning runtime includes an OpenRig agent or rig in its live backend or control loop. The application surface can be thin: structured state and specialist roles do the work, while the UI makes that work legible and steerable.

Start with the shared taxonomy

  • AI-enabled software: application code owns the control loop and calls a model as one capability.
  • Agent-Operated Workflow: an agent owns one bounded procedure with a start and stop condition; see agent-operated-workflows.
  • Agent-Operated Software: agents participate in an ongoing application's functioning runtime.

An application may compose many Agent-Operated Workflows. A bounded workflow does not by itself make its surrounding product Agent-Operated Software, and a model call is neither category unless an agent owns part of the control loop.

Agents are part of the backend

In this architecture, behavior is not located only in functions. It is distributed across agents, skills, instructions, bootstrap files, schemas, Markdown, YAML, JSON, folders, and deterministic tools. A surprising result may therefore be a code defect or a coherence gap in this control plane. Trace the path that actually produced the behavior before choosing which layer to repair.

This is not permission to tolerate defects in OpenRig core or another rock-solid substrate. There, reproduce the bug, fix the code, and hold the full gate. The faster coherence-first posture belongs to recoverable agent-operated application layers whose state and behavior can be inspected and repaired cheaply.

Markdown is the control plane

Markdown is maximally useful to an agent while remaining legible enough for a human to steer. Put intent, work state, evidence, and decisions into stable addressed artifacts rather than private chat or an opaque custom database. Keep schemas and conventions aligned with the running behavior: the agent population acts on those files as executable context.

Use progressive disclosure. A skill's name and description are the hot trigger; its body is cold procedure. Descriptions say when to load, not how to work. The body should route the reader to exact sources instead of copying them into another doctrine fork.

Scripts can act as prompts. A good script returns the context or exact effect an agent needs; when it cannot, its failure teaches what it observed, why it stopped, and safe next actions. Keep deterministic mechanics in tools and judgment in agents.

Show full SKILL.md (308 more words)Show less

Make artifacts self-certifying

When a tool produces an artifact, do not make every consumer invent a completeness test:

  1. Write to a partial path, never the final path.
  2. Verify the property that can actually be wrong, such as duration, streams, resolution, or schema.
  3. Flush and atomically rename the partial artifact to its final path.
  4. Write the manifest, then a .done sentinel last.

Consumers fail closed on the shared proof. A filename or exit code is not content verification.

Build with an agent SDLC

Select the rigor required by the outcome and the project's policy. Scope relationships, attributed evidence-backed item judgment, and genuinely distinct higher judgment have separate owners. One item judgment derives its upstream readiness; agents do not synchronize parent checkboxes, queue tags, or status prose. Capture alone is not acceptance, and readiness does not publish or advance a workflow. Use openrig-operating-model and rig proof --help for the supported judgment, correction, and read path. Keep historical locks and evidence addressable. The human supplies steering, taste, and decisions the project's authority reserves for them.

For studio applications, the running product is usually the best iteration surface. A separate mockup earns its cost only when it resolves a real design uncertainty that the running app cannot expose as cheaply. This removes a redundant artifact, not the visual review or proof contract.

Repair the narrowest authoritative layer

Find the generator or source that every affected agent actually consumes. Fix a code defect in code; fix a missing trigger in the skill; fix a malformed contract in its schema. Then verify through the consumer. Editing a rendered or installed copy creates a temporary fork, not a repair.

The payoff compounds: a correction to the shared application control plane changes the next agent's starting point. That is how an ongoing agent-operated system improves without making one human its permanent router.

© mvschwarz, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in packages/daemon/assets/plugins/openrig-core/skills/agent-operated-software of mvschwarz/openrig.

Open the folder on GitHubat commit a29dfbc

Compare with similar skills

Agent Operated Software next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Agent Operated Software compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Agent Operated Software this skillmvschwarz/openrig6.2k—~1.3kAutomated safety check: PassApache-2.0
Open Proseopenprose/prose1.8k—~7.3kAutomated safety check: NotesMIT
Create SkillPINA-org/PINA798—~1.8kAutomated safety check: PassMIT
Writing Docsc15t/c15t1.9k—~872Automated safety check: PassApache-2.0
Dex Plandcramer/dex385—~3.2kAutomated safety check: PassMIT
Planningchampionswimmer/pi-context-prune246—~779Automated safety check: PassNone

Similar skills

  • Open Prose

    openprose/prose

    Activate when the user types prose ..., opens a .prose.md file with kind: frontmatter, opens a .prose file, or asks for reusable multi-agent orchestration.

    1.8k GitHub stars~7.3k tokensUpdated 2 days ago
    Agent WorkflowsAuto-check: notes
  • Create Skill

    PINA-org/PINA

    Create, modify, and improve PINA skills. An agent skill from PINA-org/PINA.

    798 GitHub stars~1.8k tokensUpdated 3 days ago
    Agent WorkflowsAuto-check passed
  • Writing Docs

    c15t/c15t

    Author or edit c15t documentation in docs//.mdx — the source for both the c15t.com site and the docs bundled into published packages.

    1.9k GitHub stars~872 tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Dex Plan

    dcramer/dex

    Create dex task from markdown planning documents (plans, specs, design docs, roadmaps)

    385 GitHub stars~3.2k tokensUpdated 7 mo ago
    Agent WorkflowsAuto-check passed
  • Planning

    championswimmer/pi-context-prune

    Create and execute phased implementation plans stored in .agents/plans using numbered markdown files with YAML front matter and checklist steps.

    246 GitHub stars~779 tokensUpdated 8 days ago
    Agent WorkflowsAuto-check passed
  • Plannotator Annotate

    backnotprop/plannotator

    Opens Plannotator's annotation UI on a markdown file, HTML file, URL or folder, then reads the decision and feedback you send back and acts on it.

    9.2k GitHub stars~413 tokensUpdated today
    Agent WorkflowsAuto-check passed

More from mvschwarz/openrig

All 49 skills in this repo
  • OpenRig Upgrade Procedure

    mvschwarz/openrig

    Walks an agent through upgrading the OpenRig CLI and daemon one observed step at a time, keeping live seats alive and reconciling managed plugin files.

    6.2k GitHub stars~2.9k tokensUpdated today
    Auto-check passed
  • Agent Refocusing

    mvschwarz/openrig

    Re-grounds a long-running agent in the current product outcome by running a path-based trace to the root of its topology and work trees.

    6.2k GitHub stars~864 tokensUpdated today
    Auto-check passed
  • OpenRig Software Factory

    mvschwarz/openrig

    Helps set up a continuing agent software team for a real repository with OpenRig, choosing between manual work, queue handoffs and an explicit Workflow.

    6.2k GitHub stars~2.6k tokensUpdated today
    Auto-check passed
  • Separates a stable agent seat's identity from its changing occupant, and records honest, two-part provenance whenever one occupant replaces another.

    6.2k GitHub stars~2.5k tokensUpdated today
    Auto-check passed
  • Loads one section of a Markdown file by its path#h2-slug address with a bundled resolver script, for use outside OpenRig's context library.

    6.2k GitHub stars~341 tokensUpdated today
    Auto-check passed
  • Agent Starters

    mvschwarz/openrig

    Covers authoring, inspecting, refreshing, promoting and deprecating named Agent Starters, the reusable starting points for agent seats in a rig.

    6.2k GitHub stars~1.7k tokensUpdated today
    Auto-check passed

Questions about Agent Operated Software

What does Agent Operated Software do?

A skill your agent uses when designing, building, operating, or diagnosing an ongoing application whose live backend or control loop includes OpenRig agents, including applications with a Markdown…. Agent Operated Software is an agent skill from mvschwarz/openrig. Use when designing, building, operating, or diagnosing an ongoing application whose live backend or control loop includes OpenRig agents, including applications with a Markdown, YAML, or JSON agent control plane or a thin surface over specialist agent roles.

When should I use Agent Operated Software?

Agent Operated Software fits situations like: diagnosing an ongoing application whose live backend; control loop includes OpenRig agents; including applications with a Markdown; JSON agent control plane.

How do I install Agent Operated Software in Claude Code?

Run `npx skills add mvschwarz/openrig --skill agent-operated-software -a claude-code`. Or copy the skill folder (packages/daemon/assets/plugins/openrig-core/skills/agent-operated-software in mvschwarz/openrig) into .claude/skills/agent-operated-software in your project. Claude Code loads it when a task matches its description.

How do I install Agent Operated Software in Codex?

Run `npx skills add mvschwarz/openrig --skill agent-operated-software -a codex`. Or copy the skill folder (packages/daemon/assets/plugins/openrig-core/skills/agent-operated-software in mvschwarz/openrig) into .agents/skills/agent-operated-software in your project. Codex loads it when a task matches its description.

Can I use Agent Operated Software in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mvschwarz/openrig --skill agent-operated-software -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/agent-operated-software, .gemini/skills/agent-operated-software, .github/skills/agent-operated-software and .opencode/skills/agent-operated-software in your project.

What does Agent Operated Software need to run?

SKILL.md names no scripts, command-line tools or credentials: Agent Operated Software is instructions for the agent only.

Does Agent Operated Software access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Agent Operated Software safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Agent Operated Software use?

Agent Operated Software is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Agent Operated Software use?

About 1.3k tokens (SKILL.md is roughly 5.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Agent Operated Software?

Skills that share tags, products or a category with Agent Operated Software: Open Prose (openprose/prose, 1.8k stars), Create Skill (PINA-org/PINA, 798 stars), Writing Docs (c15t/c15t, 1.9k stars) and Dex Plan (dcramer/dex, 385 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Agent Operated Software?

mvschwarz (a GitHub user) maintains it in mvschwarz/openrig, which has 6,242 GitHub stars. The repository holds 49 skills in this directory. The repository was last updated on October 9, 2026.

Source: mvschwarz/openrig on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.