mcpField
U
using-agentops

using-agentops

github.com/boshu2Agent workflows450788 installsUpdated today
Repository

About using-agentops

AgentOps is an operational layer for coding agents, combining reusable knowledge, validation, skills, hooks, CLI commands, and named workflows. Its RPI flow connects research, planning, implementation, and validation with a knowledge flywheel.

Key features

  1. 01Reusable knowledge bookkeeping
  2. 02Plan and code validation
  3. 03Skills, hooks, and CLI primitives
  4. 04Research-to-validation RPI flow
  5. 05Knowledge flywheel

Use cases

  1. 01Coordinate a coding project lifecycle
  2. 02Reuse findings across agent sessions
  3. 03Validate plans and code changes
  4. 04Run parallel or autonomous issue work

MCP support

AgentOps can run as an MCP substrate through `ao mcp serve`. In this mode it orchestrates whole RPI or evolve loops handled by agents.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/boshu2/agentops --skill using-agentops

After installing, type/using-agentopsin Claude Code to confirm it loaded.

Bundled filesreferences/.gitkeepscripts/validate.sh

Details

From the project README

AgentOps Operating Model

AgentOps is the operational layer for coding agents.

Publicly, it gives you four things:

  • Bookkeeping — captured learnings, findings, and reusable context
  • Validation — plan and code review before work ships
  • Primitives — single skills, hooks, and CLI surfaces
  • Flows — named compositions like /research, /validate, and rpi

Technically, AgentOps acts as a context compiler: raw session signal becomes reusable knowledge, compiled prevention, and better next work.

Core Flow: RPI

Research → Plan → Implement → Validate
    ↑                            │
    └──── Knowledge Flywheel ────┘
Research Phase
/research <topic>      # Deep codebase exploration
ao search "<query>"    # Search existing knowledge
ao search "<query>" --cite retrieved  # Record adoption when a search result is reused
ao lookup <id>         # Pull full content of specific learning
ao lookup --query "x"  # Search knowledge by relevance

Output: .agents/research/<topic>.md

Plan Phase
/pre-mortem <spec>     # Simulate failures (error/rescue map, scope modes, prediction tracking)
/plan <goal>           # Decompose into trackable issues

Output: Beads issues with dependencies

Implement Phase
/implement <issue>     # Single issue execution
/crank <epic>          # Autonomous epic loop (uses swarm for waves)
/swarm                 # Parallel execution (fresh context per agent)

Output: Code changes, tests, documentation

Validate Phase
/vibe [target]         # Code validation (finding classification + suppression + domain checklists)
/post-mortem           # Validation + streak tracking + prediction accuracy + retro history
/post-mortem --quick   # Quick-capture a single learning (folded the retired retro lane)

Output: .agents/learnings/, .agents/patterns/

Phase-to-Skill Mapping

PhasePrimary SkillSupporting Skills
Discovery/discovery/brainstorm, /research, /plan, /pre-mortem
Implement/crank/implement (single issue), /swarm (parallel execution)
Validate/validate/vibe, /post-mortem, /forge

Choosing the skill:

  • Use /implement for single issue execution. Now defaults to TDD-first — writes failing tests before implementing. Skip with --no-tdd.
  • Use /crank for autonomous epic execution (loops waves via swarm until done). Auto-generates file-ownership maps to prevent worker conflicts.
  • Use /discovery for the discovery phase only (brainstorm → search → research → plan → pre-mortem).
  • Use /validate for the validation phase only (vibe → post-mortem → forge).
  • Use rpi for full lifecycle — delegates to /discovery → /crank → /validate.
  • Use /ratchet to gate/record progress through RPI.

Start Here (12 starters)

These are the skills every user needs first. Everything else is available when you need it.

SkillPurpose
/quickstartGuided onboarding — run this first
/bootstrapOne-command full AgentOps setup — fills gaps only
/researchDeep codebase exploration
/councilMulti-model consensus review + finding auto-extraction
/validateCanonical PASS/WARN/FAIL verdict over an artifact, plan, code change, PR, or gate
/vibeCode validation (classification + suppression + domain checklists)
rpiFull RPI lifecycle orchestrator (/discovery → /crank → /validate)
/implementExecute single issue
/post-mortem --quickQuick-capture a single learning into the flywheel
/statusSingle-screen dashboard of current work and suggested next action
/goalsMaintain GOALS.yaml fitness specification
/pushAtomic test-commit-push workflow

Advanced Skills (when you need them)

SkillPurpose
/compile, /flywheelActive knowledge intelligence and flywheel health — Mine → Grow → Defrag cycle
/curateCanonical miner role for transcripts, .agents/, bd, git, skill diffs, and rare wiki entries
/curate --mode=harvestCross-rig knowledge consolidation — sweep, dedup, promote to global hub (folded the retired harvest lane)
/injectOperationalize a mature .agents corpus into beliefs, playbooks, briefings, and gap surfaces (folded the retired knowledge-activation lane)
/brainstormStructured idea exploration before planning
/discoveryFull discovery phase orchestrator (brainstorm → search → research → plan → pre-mortem)
/planEpic decomposition into issues
/designProduct validation gate — goal alignment, persona fit, competitive differentiation
/pre-mortemFailure simulation (error/rescue, scope modes, temporal, predictions)
/post-mortemValidation + streak tracking + prediction accuracy + retro history
/bug-huntRoot cause analysis
/releasePre-flight, changelog, version bumps, tag
/crankAutonomous epic loop (uses swarm for each wave)
/swarmFresh-context parallel execution (Ralph pattern)
/using-atmRun AgentOps loops out of session on an ATM tmux swarm (the ATM leg of the substrate)
evolveGoal-driven fitness-scored improvement loop
/burndownBounded epic-completion loop — drive a finite target to all-merged, then stop
/eval-outcomesGrade via Outcomes as a holdout-safe projection of the locked eval substrate — one bar, many runtimes
/operating-loop-workflowInstall + run the operating-loop multi-agent Workflow (seven-move loop)
/autodevPROGRAM.md autonomous development contract setup and validation
agy-rules-workflowsInstall AGY-native rules, loop workflow, and scheduled goal controls
/curate --mode=dreamOut-of-session knowledge compounding lane
/docDocumentation generation — repo docs (default), gold-standard README (--mode=readme), OSS doc packs (--mode=oss)
/post-mortem --quickQuick-capture a learning (folded the retired retro lane)
/validateFull validation phase orchestrator (vibe → post-mortem → forge)
/ratchetBrownian Ratchet progress gates for RPI workflow
/forgeMine transcripts for knowledge — decisions, learnings, patterns
/securityRepository security scanning and release gating, plus the composable binary/prompt-surface suite — static analysis, dynamic tracing, offline redteam, policy gating
/testTest generation, coverage analysis, and TDD workflow
/cc-hooksAuthor and validate AgentOps runtime hook behavior
/red-teamPersona-based adversarial validation — probe docs and skills from constrained user perspectives
/reviewReview incoming PRs, agent output, or diffs — SCORED checklist
/refactorSafe, verified refactoring with regression testing at each step
/depsDependency audit, update, vulnerability scanning, and license compliance
/perfPerformance profiling, benchmarking, regression detection, and optimization
/scaffoldProject scaffolding, component generation, and boilerplate setup
/scenarioAuthor and manage holdout scenarios for behavioral validation
/skill-auditorTwo-pass audit of an existing SKILL.md against the unified template (15 checks)
/skill-builderScaffold or absorb new SKILL.md files against the unified template
/automation-shape-routingFront door for building agent automation — decide the SHAPE (Workflow vs ATM swarm vs plain skill), then hand off to the right builder
/workflow-builderScaffold a new Claude Workflow script (.claude/workflows/*.js) — deterministic multi-agent orchestration
/agent-nativeMake out-of-session agents AgentOps-native via skills + ao CLI + CI, not hooks

Expert Skills (specialized workflows)

SkillPurpose
/swarmParallel Codex agent execution (folded the retired codex-team lane)
/reverse-engineer-rpiReverse-engineer a product into feature catalog and specs
/codebase-auditDomain-parameterized codebase auditing (security, UX, performance, API, copy, CLI)
/pr-researchUpstream repository research before contribution
/pr-implementFork-based PR implementation
/validate --mode=prPR-specific validation and isolation checks (folded the retired pr-validate lane)
/pr-prepPR preparation and structured body generation
/ship-loopBot-paired internal-PR fast-lane cycle
/complexityCode complexity analysis
/productInteractive PRODUCT.md generation
/handoffSession handoff for continuation
/recoverPost-compaction context recovery
/session-bootstrapUniversal init prompt — every agent runs this first (soc-vuu6.25)
/traceTrace design decisions through history
/curate --mode=provenanceTrace artifact lineage to sources
/beadsIssue tracking operations
/heal-skillDetect and fix skill hygiene issues
/converterConvert skills to Codex/Cursor formats

To update installed skills: re-run the install one-liner — bash <(curl -fsSL https://raw.githubusercontent.com/boshu2/agentops/main/scripts/install.sh). (There is no update skill; skill refresh is an install-script concern.)

Knowledge Flywheel

Every /post-mortem promotes learnings and patterns into .agents/ so future /research starts with better context instead of zero.

Inspect, lint, and triage the .agents/ write surface contract via ao agents inspect | lint | doctor (doctor rolls up inspect + lint + orphan/stray-dir report; --strict fails on orphans).

Runtime Modes

AgentOps has several runtime modes. Do not assume hook automation exists everywhere.

ModeWhen it appliesStart pathCloseout pathGuarantees
substrate (out-of-session)A swappable orchestration substrate available out-of-session: an ATM tmux swarm, MCP (ao mcp serve), or managed-agents (ao agent)The operator or a lead agent runs bd ready and dispatches a whole loop per bead — an agent that runs the rpi skill; cron / managed triggers run maintenanceThe substrate owns the merge gate (CI-green is the signal) and triggers the knowledge-flywheel feedbackThe substrate orchestrates whole rpi/evolve loops (each an agent running the skill) — it never sees the loop's insides; the seam is substrate → agent-running-the-skill. There is no in-CLI runtime=gc executor. See agent-native and docs/3.0.md.
hook-capableClaude/OpenCode with lifecycle hooks installed (no gc)Runtime hook or ao inject / ao lookupRuntime hook or ao forge transcript + ao flywheel close-loopAutomatic startup/context injection and session-end maintenance when hooks are installed
codex-native-hooksCodex CLI v0.115.0+ with native hook support (March 2026)Runtime hooks (same as hook-capable)Runtime hooks (same as hook-capable)Native lifecycle hooks — same guarantees as hook-capable mode
codex-hookless-fallbackCodex Desktop / Codex CLI pre-v0.115.0 without hook surfacesao codex startao codex stopExplicit startup context, citation tracking, transcript fallback, and close-loop metrics without hooks
manualNo hooks and no Codex-native runtime detectionao inject / ao lookupao forge transcript + ao flywheel close-loopWorks everywhere, but lifecycle actions are operator-driven

Issue Tracking

This workflow uses beads for git-native issue tracking:

bd ready              # Unblocked issues
bd show <id>          # Issue details
bd close <id>         # Close issue
bd vc status          # Inspect Dolt state if needed (JSONL auto-sync is automatic)

Examples

Startup context loading. AgentOps 3.0's default path is explicit: run ao session bootstrap, then pull prior context with ao inject / ao lookup or a phase-scoped packet. Optional hook-capable runtimes may run an authored session-start.sh, and Codex CLI can use opt-in native hooks via install-codex.sh --with-hooks; those are compatibility/adaptor paths, not the default. Either way the agent gets the RPI workflow, prior context, and a citation path.

Workflow reference during planning. When a user asks how to approach a feature, the agent uses this skill's RPI section to recommend Research → Plan → Implement → Validate — /research for exploration, /plan for decomposition, /pre-mortem for failure simulation — instead of an ad-hoc approach.

Troubleshooting

ProblemCauseSolution
Skill not loadedStartup path not runRun ao session bootstrap, then ao inject / ao lookup; for Codex lifecycle recovery, run ao codex start explicitly
Outdated skill catalogThis file not synced with actual skills/ directoryUpdate skill list in this file after adding/removing skills
Wrong skill suggestedNatural language trigger ambiguousUser explicitly calls skill with /skill-name syntax
Workflow unclearRPI phases not well-documented hereRead full workflow guide in README.md or docs/ARCHITECTURE.md

Comments

Markdown supported