Agentops plugin for Grok Build

Community Claude Code plugin, installs in GrokPluginDeployment

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.

How to install Agentops in Grok Build

1. Add this repo as a plugin marketplace in Grok Build (once per computer):

grok plugin marketplace add boshu2/agentops

2. Install the plugin:

grok plugin install agentops@boshu2/agentops --trust
✓ Install-checked in Grok Buildchecked Oct 18, 2026

Review before you trust it. --trust lets this plugin's hooks, MCP servers and scripts run code on your computer. It's a community repo that neither xAI nor GrokStacks has reviewed, so read its code first.

Then start a new Grok session, or press r in /plugins, to load it.

Inside Grok Build: type /plugins, open the Marketplace tab, press a and add boshu2/agentops, then select agentops and press i.

Command format: Grok Build's plugin guide

What we checked: on Oct 18, 2026 it installed with grok 1.0.62 and Grok found 29 skills, 1 subagent. That's an install check only: we haven't run it in a live Grok session.

What it contains

Skills (25)

  • agent-native — Dispatch independent tasks to parallel workers or subagents without write collisions. Use when: running or planning agents in parallel, even two; check scopes before any launch.
  • agy-native — Run a supplied task in headless AGY (Antigravity, Gemini) and collect its result. Use when: AGY, Antigravity or Gemini is requested by name; never a fallback.
  • claude-exec — Run one prompt through headless Claude with scoped permissions and a time bound. Use when: scripting or automating a `claude -p` call, even a simple one.
  • codex-exec — Run one prompt through headless Codex and capture the result. Use when: wanting a one-shot `codex exec` run or CI step. Not for batches or retries.
  • council — Compare independent opinions from several models or contexts without inflating agreement. Use when: wanting a second opinion or debate, or summarizing several reviewers' results.
  • craft-goal — Draft or lint a bounded long-running goal prompt with a finish line and hard limits. Use when: selected by name; one change goes to Plan.
  • doc — Write or update READMEs, docs, repo instructions and handoff notes, checked against source. Use when: documenting something, writing a README or leaving a session handoff.
  • domain — Settle what domain terms mean per context, and which repository conventions or language standards (Go, Python) apply. Use when: names disagree or a rename is proposed.
  • idea-genie — Brainstorm evidence-backed options for what to build, or stress-test an idea. Use when: deciding what to build next, comparing options or testing an idea.
  • implement — Change or repair code, config or services without weakening tests; report what ran and what did not. Use when: implementing a change or fixing a defect.
  • interview — Interview you one question at a time, each with a recommendation, to settle a big outcome before agents work alone. Use when: selected by name.
  • memory — Write, find or curate lessons and agent rules with stated evidence and limits. Use when: asked to remember something or write a rule into agent instructions.
  • navigate — Pick the next work in an epic or bead graph; closed is not proven. Use when: asked what is next or whether an epic is done.
  • orchestrate — Coordinate several workers: what idle agents do next, which finished work gets checked first, how to recover a dead one. Use when: managing multiple agents.
  • plan — Shape a request into one end-to-end slice with observable behavior; review write scope and reversible decisions. Use when: planning, breaking down or scoping a change.
  • postmortem — Explain why a change, incident or session went as it did, separating proven causes from coincidence. Use when: a postmortem or retro is selected by name.
  • premortem — Find how a rollout plan could fail before committing to it. Use when: asked what could go wrong or to poke holes in a plan.
  • reality-check — Audit claims that work is done or shipped against the diff or repo. Use when: asked whether something really got done, even if it looks obvious.
  • refactor — Restructure or clean up code with no behavior change, proved by before-and-after checks. Use when: asked to clean up, extract, dedupe or simplify, even one function.
  • research — Answer one cited question: how code works, or whether a repeated pattern deserves a rule. Use when: asked how, why, or whether to enforce a pattern.
  • reverse-engineer — Tear down a competitor's repo or product into a feature inventory and adoption choices. Use when: comparing us to another tool or asking what to steal.
  • review — Give advisory feedback on a plan, design or code change. Use when: asked for an opinion or a look-over, even informally. Not for acceptance; use Validate.
  • rpi — Drive one accepted change through implementation and checks to done, with one fresh review only where a mistake is costly. Use when: selected by name.
  • security — Review code for security problems; scan for vulnerabilities, secrets, dependency and prompt risks. Use when: asked whether code is safe to ship, even one small handler.
  • skill-builder — Create, repair, audit or consolidate agent skills (SKILL.md packages). Use when: writing or fixing a skill, its description or structure. Not for one-off lessons; use Memory.

Subagents (4)

  • agentops:bulk-reader — Read large files or many files on the caller's behalf and return short line-referenced summaries with coverage. Use when a file exceeds the read budget or the read-budget guard blocked a Read.
  • agentops:code-reviewer — Expert code review specialist. Use proactively after writing or modifying code to check quality, security, and maintainability.
  • agentops:code-writer — Write one file from a spec plus a required reference file, matching the reference's patterns, and return a receipt (path, line count, check result) without echoing the content. Use for patterned or bo
  • agentops:researcher — Deep codebase exploration and analysis. Use for understanding code architecture, finding patterns, and gathering context before making changes.

Hooks (1)

  • hooks — PreToolUse

About this listing

Agentops is a community plugin on GitHub by boshu2, written as a Claude Code plugin that Grok Build installs. We install-checked it in Grok; we haven't run it in a live session or reviewed its code. When we installed it, Grok found 25 skills, 4 subagents, 1 hook. Its license is Apache-2.0. We checked commit bc93a662bff6. It's one of 41 listings in the Deployment category on GrokStacks. It also appears in best Grok Build plugins for deployment and hosting.

Stacks Weekly: every new Grok Build and Codex plugin, every Tuesday.

One short email for GrokStacks and CodexStacks readers, with each new plugin's install line and what it ships. Subscribe and get the free starter list: 20 Grok Build plugins worth installing first.

You'll get a confirmation email first. Unsubscribe anytime.

Agentops FAQ

How do I install Agentops in Grok Build?

Add the repo as a marketplace with grok plugin marketplace add boshu2/agentops, then run grok plugin install agentops@boshu2/agentops --trust. Then start a new Grok session, or press r in /plugins, to load it.

Is Agentops an official Grok Build plugin?

No. Agentops is a community plugin on GitHub by boshu2, not in xAI's official Grok Build marketplace. We checked that it installs and what Grok loads from it, but haven't run it in a live Grok session or reviewed its code.

What does Agentops include?

According to what Grok loaded in our install check, Agentops includes 25 skills, 4 subagents, 1 hook: agent-native, agy-native, claude-exec, codex-exec, council, craft-goal….

Details

Type
Plugin
Category
Deployment
Source
Community Claude Code plugin, installs in Grok
License
Apache-2.0
Author
boshu2
Keywords
ai-agents, claude, claude-code, claude-code-plugins, claude-marketplace, claude-skills, codex, codex-plugin, cursor, devops, opencode-plugin
Source repo
https://github.com/boshu2/agentops
Checked commit
bc93a662bff6
Homepage
https://www.12factoragentops.com
Checked by GrokStacks
Install-checked in Grok Build on Oct 18, 2026; not run in a live session

Something wrong or missing? Submit or improve this listing. Marketplace listings also refresh automatically every night.

For maintainers: badge and embeds

Maintain Agentops? Add the badge; it links to this page.

Listed on GrokStacks

Markdown

[![Listed on GrokStacks](https://grokstacks.com/badge.svg)](https://grokstacks.com/p/agentops/)

HTML

<a href="https://grokstacks.com/p/agentops/"><img src="https://grokstacks.com/badge.svg" alt="Listed on GrokStacks" width="164" height="28"></a>

Embed card (static HTML and inline CSS, no JavaScript). Preview:

<a href="https://grokstacks.com/p/agentops/" style="display:block;max-width:380px;box-sizing:border-box;padding:14px 16px;border:1px solid #2a2e3c;border-radius:12px;background:#0a0b0f;color:#e8eaf0;font:14px/1.45 -apple-system,Segoe UI,Roboto,Helvetica,Arial,sans-serif;text-decoration:none"><span style="display:block;font-size:16px;font-weight:700;color:#e8eaf0">Agentops</span><span style="display:block;margin:2px 0 8px;font-size:12px;color:#9aa0b1">Community plugin for Grok Build · 25 skills, 4 subagents, 1 hook</span><span style="display:block;margin:0 0 10px;color:#c9cdd8">DevOps discipline for AI coding agents: shape the work, track it as a graph, and get each change judged by a context…</span><span style="font-size:12px;font-weight:600;color:#7c9cff">View on GrokStacks →</span></a>

Markdown summary

**[Agentops on GrokStacks](https://grokstacks.com/p/agentops/)**: Community plugin for Grok Build with 25 skills, 4 subagents, 1 hook. Install: `grok plugin install agentops@boshu2/agentops --trust` (after `grok plugin marketplace add boshu2/agentops`)

More on badges, embeds and keeping your listing up to date: GrokStacks for plugin authors.

Also in Deployment

All 41 deployment listings →