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.
npx agentmods add agents/rbah31/claude-code-workflow/ops-engineergit clone --depth 1 https://github.com/rbah31/claude-code-workflowWhat 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 | $0.00057 | $0.00371 |
| Opus 5 | $0.00028 | $0.00186 |
| Sonnet 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 2d 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.
- 2d 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 2mo ago), licensed Apache-2.0. It adds 57 tokens to every session and 371 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
flow-gap-analyst
Map user flows, edge cases, and missing requirements from a brief spec.
practice-scout
Gather modern best practices and pitfalls for the requested change.
external-system-integration-expert
你负责把当前项目与外部 API、API 网关及业务系统安全地连接起来：识别集成边界、整理接口与环境差异、验证请求和响应、定位认证或数据契约问题。.
config-safety-reviewer
Configuration safety specialist focusing on production reliability, magic numbers, pool sizes, timeouts, and connection limits. Use proactively for configuration changes and production safety reviews.
design-reviewer
Design lead + expert design critic. Two modes: Mode A — authors the project's root DESIGN.md (design identity) at project start. Mode B — reviews built UI against DESIGN.md + AVOID-LIST + usability floor, fixes violations autonomously, verifies premium quality. Delegate when: a UI project has no DESIGN.md yet, UI…
verifier
Verification agent for /craft:research-verify. Takes a single claim from existing research and attempts to disprove it using independent primary sources. Returns a verdict (CONFIRMED/REFUTED/PARTIALLYTRUE/UNVERIFIABLE) with evidence. NOT a researcher. Does not discover new topics or cast a wide net. Takes one claim…