Help us improve
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
By boshu2
Orchestrates AI coding agents through a structured RPI (Research-Plan-Implement-Validate) workflow with persistent knowledge flywheel, git-backed task tracking, multi-agent coordination, and automated quality gates across sessions.
npx claudepluginhub boshu2/agentops --plugin agentopsExpert code review specialist. Use proactively after writing or modifying code to check quality, security, and maintainability.
Deep codebase exploration and analysis. Use for understanding code architecture, finding patterns, and gathering context before making changes.
The operator skill for the ACFS substrate. `~/acfs/bin/acfs` is a **fork-and-own provisioner** (idempotent, additive, cross-platform Mac + Ubuntu/WSL) over Dicklesworthstone's flywheel tools. This skill teaches you to check the substrate's health, wire it, and run the operating loop on top of it.
Use when coordinating agents with Agent Mail locks, inboxes, threads, and conflict-prevention handoffs.
Make an out-of-session agent AgentOps-native with skills, the ao CLI, and CI instead of hooks.
Run AGY headlessly via scheduled ticks or `agy -p`, capture agentapi JSONL evidence, and validate automated AGY loops or event streams.
Wire MCP servers and AgentOps plugin bundles into the AGY image with least-privilege access, rollback evidence, and validation hooks.
Uses power tools
Uses Bash, Write, or Edit tools
Share bugs, ideas, or general feedback.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Persistent memory, shared standards, and structured workflows for AI coding agents. Detects project setup and injects agent context automatically.
Complete project development toolkit: 23 agents, 23 slash commands, 29 lifecycle hooks, and 69 reusable skills for Claude Code workflows
Agent orchestration harness for Claude Code — campaign persistence, fleet coordination, intent routing
Harness for Claude Code — skills, /harness:* slash commands, persona subagents, lifecycle hooks, and MCP tools without per-repo `harness setup`. Sibling plugins exist for Cursor, Gemini CLI, and Codex.
Repowire mesh usage skills for AI coding agents: cross-agent review and planning, delegate, usage patterns, and install/update. Backend-agnostic and parameterised on the agent you choose.
Agent enforcement framework — context injection, planning gates, session learning
Coding agents don't do their own bookkeeping. AgentOps does. It sits on top of the agent you already use (Claude Code, Codex, Cursor, OpenCode) and adds the parts an engineering team would notice missing: a record of what was tried, gates between phases, and a corpus of learnings that survives the next session. Plain markdown in .agents/ next to your code; mix any model per phase.

/discovery → bead graph · /crank → sub-agents in waves · /validate --mixed → real Claude + Codex verdict. Live sessions. MP4
AgentOps breaks intent into bounded slices, gives each a failing test and a write scope, and makes every phase boundary a gate that records evidence. The agent starts loaded with prior decisions and learnings instead of cold:
> /council --mixed validate this PR
[council] evidence sealed → 6 judges across Claude Code + Codex CLI
[claude/judge-1] WARN rate limiting missing on /login
[codex/judge-1] WARN token bucket lacks jitter under burst
[claude/judge-2] PASS redis integration follows pattern
Consensus: WARN, fix /login limit + refill jitter before shipping
Recorded → .agents/council/<run-id>/verdict.md
Four layers that compound, all in local .agents/ you can grep, diff, and review (no telemetry, no hosted control plane):
| Layer | The problem | What AgentOps adds |
|---|---|---|
| Bookkeeping | agents forget what they tried and why | .agents/ captures runs, decisions, findings, citations, verdicts, retros |
| Context compiler | every session starts cold | ao context assemble builds phase-scoped packets; ao lookup retrieves decay-ranked knowledge |
| Validation gates | agents ship confident garbage | /pre-mortem, /vibe, /council run multi-model consensus on plans and code; gates block rather than advise |
| Knowledge flywheel | lessons vanish between sessions | /forge mines learnings, /evolve reconciles, the corpus compounds as a side effect of use |
The corpus is an LLM wiki of markdown. Agents read it natively and write to it as they work, so it maintains itself instead of becoming another doc you keep up by hand. Why that beats Notion or Confluence: docs/wiki-for-agents.md. The full theory (context as the lifecycle, the CDLC): docs/cdlc.md.
Pick your runtime, then type /quickstart in the agent.
# Claude Code
claude plugin marketplace add boshu2/agentops
claude plugin install agentops@agentops-marketplace
# Codex CLI (macOS/Linux/WSL). OpenCode: install-opencode.sh
curl -fsSL https://raw.githubusercontent.com/boshu2/agentops/main/scripts/install-codex.sh | bash
# Codex CLI (Windows):
irm https://raw.githubusercontent.com/boshu2/agentops/main/scripts/install-codex.ps1 | iex
# Gemini / Antigravity
curl -fsSL https://raw.githubusercontent.com/boshu2/agentops/main/scripts/install-agy.sh | bash
# Other skills-compatible agents
npx skills@latest add boshu2/agentops --cursor -g
The ao CLI is optional but recommended (bookkeeping, retrieval, health, the loops):
brew tap boshu2/agentops https://github.com/boshu2/homebrew-agentops && brew install agentops # macOS
# Windows: irm https://raw.githubusercontent.com/boshu2/agentops/main/scripts/install-ao.ps1 | iex
# Or release binaries / build from source (cli/README.md).
Installs hookless: skills and the ao CLI guide the workflow, and the local cockpit gate is the release authority. GitHub Actions are an optional/manual backstop, not the routine shipping path. The only hard requirement is an agent runtime and git; everything else degrades gracefully. Full dependency matrix: docs/dependencies.md. Day-2 install, update, backup, permission, recovery, and escalation paths are in docs/install-day2-ops.md.