agentops
boshu2 · boshu2/agentops
Provides a DevOps framework and skills for AI coding agents to shape work, track progress as a graph, and get changes judged by an independent context.
DevOps discipline for AI coding agents: shape the work, track it as a graph, and get each change judged by a context that didn't write it.
Preview
What you can do with it
- Establish repeatable agentic coding sessions with automated checks and feedback.
- Preserve work graphs, decisions, results, and project memories for future agent sessions.
- Guide agent decisions and check specific contracts through customizable skills and executable gates.
Safety check
Usable, but read the notes first.
- ●Installer downloads a remote script and pipes it to the shell.
scripts/install-bd.sh
Automated scan of the repo files. Always review code you run.
From the README
AgentOps
DevOps discipline for AI coding agents.
Install · The loop · Goals · Try it · Skills · Make it yours · Evidence · Beyond AgentOps
DevOps makes software delivery repeatable through shared practices, automated checks and feedback. AgentOps brings that discipline to agentic coding sessions: paved paths your agents can follow from intent to checked results, with memory to carry useful context into the next task.
Those paths combine skills with the ao CLI
and your existing engineering tools. Plan clarifies the
expected behavior; Test helps check it;
Validate adds independent judgment where needed.
Skills guide the agent's decisions; executable gates check specific contracts.
Beads preserves the work graph, decisions,
results and project memories. Memory curates supported
findings into linked project knowledge, connecting lessons to the work and
sources behind them. The next session can use that record instead of starting over.
The skills are a kit, and you are expected to change it. Each skill is one Markdown file of instructions. Keep the ones that fit how you work, rewrite the ones that almost fit, delete the rest, and add skills you write yourself or find in other libraries. What you end up with is your own operating model for agents, which is the reason this project exists. Make it yours shows how.
Use these paths with Claude Code, Codex, Cursor, OpenCode, Gemini CLI, Pi and other coding agents, or personal assistants such as OpenClaw and Grok Bot. Start with one useful task; follow the operational loop for a change or the goal workflow for work across sessions. When you need a larger software factory, extend the same practices with Gas City or tools from the Agentic Coding Flywheel.
Why use AgentOps?
A software factory makes engineering practices reusable through tools, guidance and repeatable workflows. AgentOps brings that approach into the coding session: clear intent, automated checks, recorded decisions and a feedback loop into later work. Pick the path your task needs and use the same practices when you change agents.
Behavior-driven development (BDD) starts by agreeing on what the software should do in a concrete situation. For retries, that could mean: “If a completed job arrives again, return its result and charge the customer only once.” The same behavior guides the implementation, its tests and any review. Plan helps you settle those expectations before the agent starts editing.
| When you need to… | AgentOps adds |
|---|---|
| Get the agent to build what you meant | Plan makes the expected behavior clear enough to implement and test. Domain keeps the same names for concepts in the request, code and tests. |
| Keep a project moving after the chat ends | Interview settles a large goal with you. Beads preserves its intent, decisions and results in a searchable work graph, with persistent project memories for later sessions. Navigate identifies ready work, blockers and gaps in the goal. |
| Check whether the finished change meets the request | Test helps write checks for the intended behavior. Ordinary changes finish on checks and CI; Validate adds one fresh review when requested, hard to undo, or uncovered by a deterministic check. |
| Turn earlier work into useful context | Research traces the code and cites what it finds. Memory can draw on Beads handoffs, Git changes and check results to explain a decision in a report, or curate supported lessons into reviewed project documents. Later agents can recall the lesson and follow its sources. |
| Make a useful method repeatable | Skill Builder turns supported expertise into guidance with clear inputs, actions and limits. Skill Eval measures whether that guidance helps a named task, so it can be retained, revised or removed. |
Quickstart
Pick one method per agent: a plugin plus npx on the same agent gives you every skill twice.
Claude Code
claude plugin marketplace add boshu2/agentops
claude plugin install agentops@agentops-marketplace
claude plugin details agentops@agentops-marketplace
Check that agentops appears in the plugin inventory. The bundle includes
skills, four agents and tool-call guards.
Codex
codex plugin marketplace add boshu2/agentops
codex plugin add agentops@agentops-marketplace
codex plugin list --json
Check that agentops appears in the inventory. Skills use the agentops: prefix;
custom roles and read limits have separate setup.
Everything else (Cursor, OpenCode, Gemini CLI, Pi, OpenClaw, Grok Bot)
With Node.js installed, run from your project directory, then pick your agents and skills:
npx skills@latest add boshu2/agentops
Add -g for a user-level install. In scripts, name the agents:
npx skills@latest add boshu2/agentops -g -a cursor opencode -y
(-y without -a can install into every agent the installer knows).
Installer targets include cursor, opencode, gemini-cli, antigravity,