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/fockus/skill-memory-bank/mb-devopsgit clone --depth 1 https://github.com/fockus/skill-memory-bankWhat 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.00043 | $0.00772 |
| Opus 5 | $0.00022 | $0.00386 |
| Sonnet 5 | $0.00009 | $0.00154 |
| Haiku 4.5 | $0.00004 | $0.00077 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 51 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 prepended by/mb work— 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.
- 2d 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 (25 stars, last pushed 1mo ago), licensed MIT. It adds 43 tokens to every session and 772 once invoked, about $0.0002 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-30.
Other agents, from other repositories
vc-innovate-agent
INNOVATE MODE - Brainstorming and exploring implementation approaches. Discusses possibilities without making decisions. Use after research is complete.
tool-conflict-agent
An agent with conflicting tool configurations.
invalid-target
Review pull requests.
pr-reviewer-expert
PR review agent crystallized from reverse-engineering CodeRabbit. Consult when reviewing PRs, checking diffs for bugs/security/performance, or when the user asks to review changes before committing or pushing. Trigger conditions: git diff output, PR descriptions, "review this", "check these changes", pre-push review…
plan-creation-eng-lead
Engineering and Delivery Lead for implementation planning. Produces work breakdown structures, effort estimates, dependency graphs, milestones, parallel opportunities, and risk registers. Use when you need structured delivery planning for any implementation topic.
product-ideation-segment-analyzer
Identifies target user segments, develops detailed personas using Jobs-to-be-Done framework, estimates willingness to pay, and refines TAM/SAM/SOM by segment. Reads competitive analysis output from logs/. Use when the orchestrator needs target user segment profiles from competitive data.