The operational layer for coding agents. Memory, validation, and feedback loops that compound between sessions.
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 next to your code; mix any model per phase. /discovery → bead graph…
⚠ The trust score below reflects the collection's repository only. The bundled units are not individually verified or scanned — review them before use.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
The repository archive could not be read at scan time (The operation was aborted due to timeout), so no tool declarations could be extracted from it. Nothing here is a statement about what this exposes.
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 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…
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.