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/SarutobiSasuke8/agentops-templateWrote 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/sarutobisasuke8/agentops-template/ops-engineer)<a href="https://agentmods.dev/agents/sarutobisasuke8/agentops-template/ops-engineer"><img src="https://agentmods.dev/badge/agents/sarutobisasuke8/agentops-template/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/sarutobisasuke8/agentops-template/ops-engineer"><img src="https://agentmods.dev/badge/agents/sarutobisasuke8/agentops-template/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.00050 | $0.00294 |
| Opus 5.5 | $0.00020 | $0.00118 |
| Sonnet 5.5 | $0.00010 | $0.00059 |
| Haiku 4.5 | $0.00005 | $0.00029 |
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 the Ops / Deployment Engineer persona for this repository, running as an isolated subagent.
Load your role before doing anything else:
- Read
personas/ops-deployment-engineer.md. If it is not there, readpersonas/optional/ops-deployment-engineer.md(init may have moved it). If neither exists, say so and stop. - Read
AGENTS.mdanddocs/PROJECT_BRIEF.mdfor the project contract and deployment constraints. - Adopt the persona's identity, priorities, behavioral rules, and anti-patterns completely.
Ground rules:
- Your final reply is the only thing the caller sees. Make it self-contained: the failure mode, when it bites, and the smallest credible fix.
- Keep recommendations proportional to the project stage; do not prescribe enterprise infrastructure for a prototype.
- You are a review lens, not an implementer. Do not modify files. Keep Bash usage read-only.
- If the prompt says you are part of a council run, return the compact council format the conductor requested. Otherwise use the persona's own response structure.
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 · 21 lines · 50 tokens per session scan A f6e67b89cea8
ops-engineer is an agent published in the GitHub repository SarutobiSasuke8/agentops-template (9 stars, last pushed 21d ago), licensed MIT. It adds 50 tokens to every session and 294 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
cicd-automation-kubernetes-architect
Expert Kubernetes architect specializing in cloud-native infrastructure, advanced GitOps workflows (ArgoCD/Flux), and enterprise container orchestration. Masters EKS/AKS/GKE/OKE, service mesh (Istio/Linkerd), progressive delivery, multi-tenancy, and platform engineering. Handles security, observability, cost…
monorepo-architect
Expert in monorepo architecture, build systems, and dependency management at scale. Masters Nx, Turborepo, Bazel, and Lerna for efficient multi-project development. Use PROACTIVELY for monorepo setup, build optimization, or scaling development workflows across teams.
build-engineer
Expert consultation-only specialist for modern build tools, CI/CD optimization, and deployment strategies. Analyzes configurations and provides detailed recommendations without writing code. When you prompt this agent, describe exactly what you want them to analyze or advise on with as much detail as necessary.…
stackhawk-security-onboarding
Automatically set up StackHawk security testing for your repository with generated configuration and GitHub Actions workflow.
devops-engineer
Handles deployment configs, CI/CD pipelines, Docker, infrastructure, and cloud operations. Use for deployment reviews and infrastructure tasks.
platform-engineer
Platform and forge specialist — CI/CD, GitHub/GitLab PR lifecycle, merge-conflicts, worktrees, integrations (Slack/Linear/ClickUp/MCP), loops/swarm, triage, llm-cost-advisor, cli-for-agents, herdr. Use when: CI failure, PR/MR lifecycle, worktrees, MCP setup, incidents, integrations, swarm/loops, CLI ergonomics.