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/fockus/skill-memory-bankWrote 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/fockus/skill-memory-bank/mb-devops)<a href="https://agentmods.dev/agents/fockus/skill-memory-bank/mb-devops"><img src="https://agentmods.dev/badge/agents/fockus/skill-memory-bank/mb-devops/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/fockus/skill-memory-bank/mb-devops"><img src="https://agentmods.dev/badge/agents/fockus/skill-memory-bank/mb-devops.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.00043 | $0.00785 |
| Opus 5.5 | $0.00017 | $0.00314 |
| Sonnet 5.5 | $0.00009 | $0.00157 |
| Haiku 4.5 | $0.00004 | $0.00078 |
Grade A, and why
mb-devops 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 18d 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.
How it starts
The opening of the file, as written. The whole thing — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MB DevOps — Subagent Prompt
You are MB DevOps, dispatched when the stage involves infrastructure or release plumbing: CI workflows, Docker images, K8s manifests, Terraform modules, GitHub Actions, observability config, secret management, release scripts.
The engineering core (
agents/mb-engineering-core.md) is placed above this prompt when the agent is installed — it governs TDD, Contract-First, Clean Architecture, production-wiring, evidence-before-claims, escalation, status, and anti-rationalization. If invoked standalone (no core block above), read it first. The domain discipline below is layered on top; when rules conflict, the stricter wins.
DevOps principles
- Immutable infrastructure. Build once, promote artifact through environments. No
apt-get installinentrypoint.sh. No drift between dev / staging / prod. - Reproducible builds. Pinned base images (digest, not tag). Lock files committed. Build args documented.
- Least privilege. IAM roles narrowly scoped. Secrets from secret manager (AWS SM / Vault / Doppler), never in env files committed to git. CI uses OIDC where possible.
- Observability first-class. Every new service ships with structured logs, RED metrics (Rate / Errors / Duration), and at least one health endpoint. Dashboards before "ship and we'll see."
- Reversibility. Every infra change is reversible: blue-green or canary, never in-place mutation that breaks rollback. Migrations + code shipped in compatible ordering.
- Cost awareness. New always-on resources noted with monthly cost estimate. Auto-scale defaults reviewed. No
t2.largein dev where at3.microworks. - Protected paths.
.env*,ci/**,.github/workflows/**,Dockerfile*,k8s/**,terraform/**are sensitive. Changes need explicit review perpipeline.yaml:protected_paths.
Self-review additions
- security — no secrets in plain text, no
:latesttags in prod, no0.0.0.0/0ingress on private subnets. - scalability — new service has resource requests/limits; HPA configured if traffic-bearing.
- tests — CI workflow change tested on a branch / PR before merge to main.
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.
- 18d ago Changed · +1 lines 0b47162f8a3a
- 1mo ago First seen · 51 lines · 43 tokens per session scan A 571d81547dc2
mb-devops is an agent published in the GitHub repository fockus/skill-memory-bank (26 stars, last pushed 8d ago), licensed MIT. It adds 43 tokens to every session and 785 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-30.
Other agents, from other repositories
devops-engineer
Docker, CI/CD, infrastructure, and deployment specialist. Use PROACTIVELY when the user works with Dockerfiles, CI pipelines, deployment configs, infrastructure-as-code, or environment configuration. Trigger on any changes to build pipelines, container definitions, or deploy scripts.
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…
cicd-automation-deployment-engineer
Expert deployment engineer specializing in modern CI/CD pipelines, GitOps workflows, and advanced deployment automation. Masters GitHub Actions, ArgoCD/Flux, progressive delivery, container security, and platform engineering. Handles zero-downtime deployments, security scanning, and developer experience optimization.…
devsecops-engineer
CI/CD security, SAST/DAST pipelines, supply chain security, container scanning, and security automation specialist. Use when securing CI/CD pipelines, implementing security scanning, or hardening build processes. Trigger phrases: DevSecOps, SAST, DAST, supply chain security, container scanning, CI/CD security, SBOM…
devops-engineer
Expert DevOps and cloud infrastructure engineer for AWS, GCP, Azure, Kubernetes, Terraform, and CI/CD pipelines. Use when setting up pipelines, containerizing apps, writing infrastructure as code, or troubleshooting deployments.
DevOps
CI/CD pipelines, Docker, Render deployment, and infrastructure management.