by boshu2
The operating loop a coding agent follows — and skills to orchestrate multi-agent systems.
# Add to your Claude Code skills
git clone https://github.com/boshu2/agentopsLast scanned: 5/26/2026
{
"issues": [],
"status": "PASSED",
"scannedAt": "2026-05-26T07:46:23.789Z",
"semgrepRan": false,
"npmAuditRan": true,
"pipAuditRan": true
}agentops is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by boshu2. The operating loop a coding agent follows — and skills to orchestrate multi-agent systems. It has 412 GitHub stars.
Yes. agentops passed SkillsLLM's automated security scan — a dependency vulnerability audit plus prompt-injection heuristics — with no high-severity issues. You can read the full report in the Security Report section on this page.
Clone the repository with "git clone https://github.com/boshu2/agentops" and add it to your Claude Code skills directory (see the Installation section above).
agentops is primarily written in Go. It is open-source under boshu2 on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other AI Agents skills you can browse and compare side by side. Open the AI Agents category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh agentops against similar tools.
No comments yet. Be the first to share your thoughts!
AgentOps is the operating loop a coding agent follows: one intent, one bounded
build, one fresh judge, one durable verdict. It also ships skills to orchestrate
multi-agent systems. For contested calls, opt into
council (independent judges) or
idea-genie duel mode (sealed perspectives
before Plan).
RPI -> Plan -> Implement -> fresh Validate -> durable verdict -> report and stop
brew install beads
npx skills@latest add boshu2/agentops --all -g
Use plan, implement, validate, and learn — or
rpi to run the loop once.
Prefer a managed bundle that updates with the release:
# Claude Code
claude plugin marketplace add boshu2/agentops
claude plugin install agentops@agentops-marketplace
# Codex
codex plugin marketplace add boshu2/agentops
codex plugin add agentops@agentops-marketplace
Two install paths:
Remove with your runtime's plugin uninstall, or delete the linked skill directories.
Beads is the preferred tracker. Plan
writes BDD acceptance and DDD ubiquitous
language into the bead;
Implement builds against it; Validate judges a hashed snapshot under
.agents/ao/intents/sha256/. No beads? Plan shapes the caller's issue or chat
text and the runtime snapshots those bytes the same way.
validate must run in a fresh context (not the author session). Same model or
a different one — both are supported.
The default loop is one agent, one writer. When you need a fleet,
swarm, agent-native,
ntm, and using-gc
orchestrate multi-agent work. They dispatch; they do not own the verdict.
AgentOps already borrows heavily from that ecosystem. Two stacks people run around the same loop:
ao CLIDeterministic checks, inspection, and skill linking. Skip it if you only need the skills.
brew tap boshu2/agentops https://github.com/boshu2/homebrew-agentops
brew install agentops
Without Homebrew: go install github.com/boshu2/agentops/cli/cmd/ao@latest
To track skills from a local checkout instead of a release bundle, run
ao skills link from that checkout.
Same session that wrote the code also declared victory. AgentOps separates
authorship from judgment: implement produces a candidate; validate must
run in a fresh context and may use a different model. It issues PASS,
FAIL, or NOT_PROVEN.
A single context can share blind spots with the author. Opt into
idea-genie or council
for sealed or multi-judge review. They return a report;
validate writes verdict.v2.
Without a fixed behavior and write scope, "done" is whatever the agent
improvised. plan locks acceptance in the bead before anyone builds. Later
phases bind to that digest.
Chat scrolls away. validate writes a content-addressed verdict.v2 under
.agents/ao/verdicts/sha256/ with checked scope, omissions, and evidence
refs. Plain JSON. No hosted service required.
| Skill | Job |
|---|---|
rpi |
run Plan, Implement, and fresh Validate at most once |
plan |
create the bead (BDD + DDD ubiquitous language) |
implement |
TDD against the bead: RED → GREEN → refactor |
validate |
fresh context (optionally different model); persist verdict.v2 |
Optional later: learn. Strategies:
council, idea-genie,
premortem, postmortem.
AgentOps prefers a smaller skill set you can steer over dozens of near-duplicate skills. Modes and flags change behavior inside one contract.
| Skill | Steer with | Examples |
|---|---|---|
doc |
--mode |
readme, oss, default API/docs; README mode runs a docs-prose (de-slop) pass |
codebase-recon |
mode · view · lens · depth | baseline/delta; emphasize audit or mental model; one domain lens per pass |
idea-genie |
elicit | duel | portfolio vs sealed multi-perspective challenge |
rpi |
bead / intent ref | one full loop against a frozen bead |
Read the skill's mode table before inventing a sibling skill. Full inventory: Skill Router.
A PASS binds unchanged acceptance, a deterministic subject manifest, complete
changed-path coverage inside write scope, distinct author and validator context
IDs, a freshness attestation, and criterion-level evidence.
Missing identity, mutation, or incomplete coverage → NOT_PROVEN. Proven
out-of-scope change or failed criterion → FAIL.
Operating loop · CLI · Docs
Contributing: docs/CONTRIBUTING.md. License: Apache-2.0.