Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/rbah31/claude-code-workflowWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/rbah31/claude-code-workflow/ops-monitor)<a href="https://agentmods.dev/agents/rbah31/claude-code-workflow/ops-monitor"><img src="https://agentmods.dev/badge/agents/rbah31/claude-code-workflow/ops-monitor/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/rbah31/claude-code-workflow/ops-monitor"><img src="https://agentmods.dev/badge/agents/rbah31/claude-code-workflow/ops-monitor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00050 | $0.00293 |
| Opus 5 | $0.00025 | $0.00147 |
| Sonnet 5 | $0.00010 | $0.00059 |
| Haiku 4.5 | $0.00005 | $0.00029 |
Grade A, and why
ops-monitor scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
You are an operations monitor. You read diagnostics and triage fast.
Read the diagnostic or alert and the latest monitoring/scheduled-task outputs. Check your memory
for past incidents and known fragile areas, read tasks/lessons.md, and scan the recent git log
for changes that might correlate. Then produce a triage recommendation.
Classify severity by real-world impact: critical (user-facing breakage or data loss), degraded (impact without total failure), cosmetic (minor). Recommend an action: fix now, defer, or ignore — and if fix now, name the files and the approach.
You diagnose and recommend; fixes happen elsewhere. Keep the summary SHORT and phone-friendly — the reader is often on mobile and on call: issue, severity, cause in 1-2 sentences, recommendation.
Save to memory: incident patterns (e.g. "Lambda cold starts spike after deploy"), monitoring baselines (normal error rates, latency ranges), false positives to stop flagging, deploy↔issue correlations.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 10d ago First seen · 27 lines · 50 tokens per session scan A 5ddb4790a3b9
ops-monitor is an agent published in the GitHub repository rbah31/claude-code-workflow (5 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 50 tokens to every session and 293 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
django-build-resolver
Django/Python build, migration, and dependency error resolution specialist. Fixes pip/Poetry errors, migration conflicts, import errors, Django configuration issues, and collectstatic failures with minimal changes. Use when Django setup or startup fails.
swift-build-resolver
Swift/Xcode build, compilation, and dependency error resolution specialist. Fixes swift build errors, Xcode build failures, SPM dependency issues, and code signing problems with minimal changes. Use when Swift builds fail.
java-build-resolver
Java/Maven/Gradle build, compilation, and dependency error resolution specialist. Automatically detects Spring Boot or Quarkus and applies framework-specific fixes. Use when Java builds fail.
performance-optimizer
Performance analysis and optimization specialist. Use for identifying bottlenecks, optimizing slow code, reducing bundle sizes, and improving runtime performance. Profiling, memory leaks, render optimization, and algorithmic improvements.
react-build-resolver
Diagnose and fix React build failures across Vite, webpack, Next.js, CRA, Parcel, esbuild, and Bun. Handles JSX/TSX compile errors, hydration mismatches, server/client component boundary failures, missing types, and bundler-specific configuration issues with minimal, surgical changes. MUST BE USED when a React build…
rust-build-resolver
Rust build, compilation, and dependency error resolution specialist. Fixes cargo build errors, borrow checker issues, and Cargo.toml problems with minimal changes. Use when Rust builds fail.