Agent Ops: five rules for agents on a live service, and a five-check script (free sample)
by PaperChaseWebb
From the Agent Ops bundle: five rules for running agents on a service people use (one named approver, a stop tested in the last 30 days, risky actions owner-yes, voice never approves, a watch on every live change), and a read-only script that checks one small file for them.
- Price
- Free
- Difficulty
- Beginner
- Setup
- 5 min
- Format
- .md file
agent-ops-five-rules-for-agents-on-a-live-service-free-sample.md · 7 KB · direct download, no signup
What you end up with
In a few minutes you can see which ops decisions are missing before an agent rolls something back on its own.
What you get
- Five ops rules
- ops_mini.py: five read-only checks on one ops-lite.json
- One prompt for all four harnesses
- Worked example: 5 findings, then 0
Who it is for
Anyone running two or more agents on a live service who wants a quick check of the basics first.
Works with
Solid chips: the agent is named in this listing's own tools list. Dashed chip: Plain Markdown, so it also pastes into other agents such as Grok Bot, Hermes, OpenClaw or Muse. We list those as compatible by format only, not as tested.
Tools needed
Cost to run: Free.
Time to result: About five minutes to a first result
Sample prompts, free to use
Read ops-lite.json for the service we run. Run ops_mini.py on it and show me the output. For each finding, tell me the smallest fix and what you need from me. Do not fill in stop dates yourself, and do not take any action from the list.
The rules and the script are in the file.
Free preview of the file
# Agent Ops: five rules for running agents on a live service, and a five-check script (free sample)
Version 1.0, 2026-10-29. By PaperChaseWebb. For solo builders and small teams running two or more agents in Grok Bot, Claude Code, Codex or Hermes on a service people use. One Markdown file and one Python 3 script, standard library only. The script was tested on its worked example (5 findings, then 0) and on a missing file (exit 2). It was not run inside any agent harness or on a live system.
Most trouble with agents on a live service comes from a few missing decisions. Nobody is named as the person who approves. A stop was never tried. A rollback was marked as something the agent may do alone. A word said out loud counted as a yes. A change went live and nothing watched it. This sample gives you the five rules that cover those, and a script that checks them on one small file.
## Install in one line
Save this page as FREE-SAMPLE.md, then:
```
python3 -c "import re;t=open('FREE-SAMPLE.md').read();open('ops_mini.py','w').write(re.search(r'~~~python\n(.*?)~~~',t,re.S).group(1))"
python3 ops_mini.py ops-lite.json
```
## Five ops rules
1. **One named person approves risky actions.** Not "the team". That person types the yes.
2. **Every agent's stop was tested in the last 30 days.** You stop it yourself, on purpose, and write the date. The agent never fills that in.
3. **Risky actions are owner-yes.** Rollback, flag flips, alert changes, deploys, merges, key rotation, auth chaTest record
- Date
- Oct 29, 2026
- What was run
- ops_mini.py on the worked example, a fixed file and a missing file.
- Result
- 5 findings, then 0; exit 2 on a missing file.
- Not run
- The prompt inside a harness.
Copied from this item's dated test notes. What was not run stays in.
Worth knowing
- The sample checks one file against five rules. The full Ops Runbook, gate, request approvals by hash, drills, surface decisions and the fifteen checks are in the full bundle.
- On 2026-10-29 ops_mini.py gave 5 findings on the worked example, then 0 on the fixed file, and exited 2 on a missing file. The prompt was not run inside a harness. The example dates are relative to that day; change them to recent dates before running it.
Questions
Does it send anything anywhere?
No. It reads one file and opens no network connection.
What is in the full bundle?
The Ops Runbook with fifteen checks and owner approval tied to each request's hash, plus Release Watch, Agent Control Room, Agent Status Hardware and Shrink the Attack Surface in full. $69, against $106 for the four bought separately.
Details
Version 1.0 · Updated Oct 29, 2026 · Markdown version of this page
License: Personal and commercial use. Download terms
Related
Agent Ops bundle: run a service and its agents from one runbook a script can check
Release Watch, Agent Control Room, Agent Status Hardware and Shrink the Attack Surface in full, tied into one daily loop by a new Ops Runbook: plain files for agents and their owners, tested stops, room names and lights, watched changes, attack surface decisions with proofs, action gates and monthly drills. ops.py answers every action with go, ask the owner or never, and a fifteen-check script names every gap. A risky action waits for the owner's yes typed at their terminal and tied to that request's sha256.
Release Watch: a per-change monitoring plan your agent writes from the diff, run by a fixed script
After a change goes live, your agent reads the diff and writes a small watch plan for that change: which signals it could move, against which baseline, by how much, for how long. A fixed script runs the plan every five minutes, so no agent sits in a loop. On a trip, a second agent triages read-only and proposes one next step. Rollbacks, flag flips and alert changes stay with you.
Agent Control Room: voice control for a dozen agents
Talk to twelve agents by name from one place. Say "tell juniper to fix the login test" and it goes to juniper and only juniper, read back in a sentence. Ask "who is waiting" and the board answers with waiting on top. Say "stop all" and every session gets it. What voice never does is approve: every yes, "approve it", "go ahead" and "1" is refused, and gated actions wait for a typed yes from the owner tied to the sha256 of the request, which the agent checks before it acts.