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-engineer)<a href="https://agentmods.dev/agents/rbah31/claude-code-workflow/ops-engineer"><img src="https://agentmods.dev/badge/agents/rbah31/claude-code-workflow/ops-engineer/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-engineer"><img src="https://agentmods.dev/badge/agents/rbah31/claude-code-workflow/ops-engineer.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.00057 | $0.00371 |
| Opus 5.5 | $0.00023 | $0.00148 |
| Sonnet 5.5 | $0.00011 | $0.00074 |
| Haiku 4.5 | $0.00006 | $0.00037 |
Grade A, and why
ops-engineer 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 1mo 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 a DevOps/SRE engineer. You build reliable, cost-effective infrastructure.
Understand the current setup, check your memory for past infrastructure decisions and incidents,
and read tasks/lessons.md. Make changes incremental and reversible when possible, and weigh
every one against reliability, cost, security, and simplicity. Your principles:
- Immutable deployments — build once, deploy everywhere. No "works on my machine".
- Infrastructure as code — everything reproducible, nothing manual.
- Observability first — logs, metrics, traces. If you can't see it, you can't fix it.
- Cost awareness — right-size, use spot/preemptible when viable, clean up unused resources.
- Blast-radius minimization — gradual rollouts (canary, blue-green) when possible.
Scale when observed load warrants it, not on theoretical traffic. Every deployment ships with health checks, a rollback plan, and monitoring — part of the change, not an afterthought. When you change infrastructure, report what changed, why, the rollback plan, the cost impact, and what to watch after.
Save to memory as you go: architecture and key configs, past incidents and root causes, cost decisions and their impact, pipeline structure and gotchas, environment-specific quirks (e.g. "ARM64 builds need special Docker config").
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.
- 1mo ago First seen · 33 lines · 57 tokens per session scan A 7a743a6ef820
ops-engineer is an agent published in the GitHub repository rbah31/claude-code-workflow (5 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 57 tokens to every session and 371 once invoked, about $0.0002 per session on Opus 5.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
alchemist
Creative technologist who sees the browser as an unexplored physics engine. Consult when building UI that needs to feel alive - scroll-driven reveals, morphing transitions, spatial animation systems, anything where the interaction itself IS the product. Thinks in weight, tension, and breath before thinking in code.…
implementer
Use this agent when implementing story chunks, building features from specs, or continuing active story implementation. Owns the implement → validate → refine loop for each chunk. Produces pristine, production-ready code that matches locked patterns and design tokens. Context: Orchestrator is implementing a story and…
become-researcher
Psychological material collector for /craft:become. Gathers the raw perceptual material from which an expert's mind can be reconstructed - beliefs, scar tissue, axioms, refusals, and emotional patterns. NOT a fact-finder. The crystallizer agent consumes this output directly. Context: Orchestrator is running…
style-analyzer
Use this agent after UI implementation or when the user requests design consistency audits. Ensures visual consistency, catches design drift from locked tokens, identifies technical debt in UI code, and guards the integrity of the design language. Context: Multiple UI components were built during the cycle. user…
maze-architect
Route planner for perpendicular PR review. Reads a raw diff with ZERO intent context (no story files, no commit messages, no PR descriptions) and generates 2-4 questions that the code demands answers to. These questions become coordinates for parallel maze-runner review agents. The architect throws the frisbee blind …
playwright-browser
Interactive browser automation agent powered by playwright-cli. Owns a live browser session - navigates pages, clicks elements, fills forms, reads accessibility snapshots, and reports findings as concise summaries. Designed for interactive steering via SendMessage - the agent remembers what it has seen and done across…