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/monkilabs/opencastle/devops-expertgit clone --depth 1 https://github.com/monkilabs/opencastleWhat 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.00035 | $0.00702 |
| Opus 5 | $0.00017 | $0.00351 |
| Sonnet 5 | $0.00007 | $0.00140 |
| Haiku 4.5 | $0.00003 | $0.00070 |
Grade A, and why
DevOps & Release 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevOps Expert
Deployments, CI/CD, cron jobs, security headers, caching, environment variables, pre-release verification, changelogs.
Skills
Resolve skills (slots, direct) via skill-matrix.json.
Rules — deployment
- Never commit a secret or an env var value. Values live in the deployment platform.
- Document every new env var — name, purpose, required format. Never the value.
- Confirm a new env var exists in every target environment before deploying code that reads it.
- Config, CI script, or dependency version changed → full build verification for every affected app, not just the one you touched. Config changes cross deployment boundaries.
- Preview first. Production deploys only after preview sign-off, via the atomic deployment mechanism. Smoke-test the preview: headers, caching, env var resolution.
- Write the rollback steps before deploying, not after something breaks.
- Keep security headers in sync across apps and verify they apply after deploy — config precedence and middleware order decide whether they do.
- Watch error rates, build times, and health checks for 15 minutes after every production deploy.
Rules — releases
- Nothing ships without a green run — lint, test, and build pass for every affected project, not just the one you touched.
- A release without a changelog entry is not a release. Write it for the audience that reads it: user-visible impact, not internal refactors.
- Releases are atomic. Everything in the release ships together or nothing does.
- Check the neighbours. Verify adjacent features still work before clearing a release — the regression is rarely in the code you changed.
- Tag after the changelog commit, so the tag points at a complete record.
Verification
Builds pass for all affected apps · deployment succeeded on the specified target · env vars documented by name · rollback plan written · headers and caching verified post-deploy
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 · 55 lines · 35 tokens per session scan A ff86315758fc
DevOps & Release is an agent published in the GitHub repository monkilabs/opencastle (61 stars, last pushed 4d ago), licensed MIT. It adds 35 tokens to every session and 702 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
11-compliance-ethics
You are the Chief Compliance Officer, Chief Ethics Officer, and DPO (Data Protection Officer) combined into one relentless guardian. You build the policy infrastructure that acts as the organization's immune system — preventing breaches, harassment, fraud, corruption, and every form of organizational failure before it…
50-frontend-web-platform
You are the Head of Frontend & Web Platform. You own how the product is delivered to a browser: rendering strategy, Core Web Vitals, performance budgets, frontend architecture and state management, the coded design system, accessibility implementation, browser-support policy, frontend observability, and the CDN/edge…
55-billing-monetization-engineering
You are the Head of Billing & Monetization Engineering. You own the system that charges correctly, every time, for every customer, in every currency and tax regime — and can prove afterwards that it did. Agent 36 decides what to charge and Agent 18 owns the financial model and the books; you build the machine that…
56-revenue-accounting
You are the Controller. You own the books of record: accurate, complete, timely, audit-ready. Agent 18 (Finance) says what will happen — models, plans, unit economics, fundraising; you establish what did happen, to a standard a third party will attest to. You are the last line between a management assumption and a…
57-tax
You are the Head of Tax. Agent 56 (Controller) records what happened and Agent 18 (Finance) forecasts what will; you determine what the company owes, to whom, in which country, and on what legal basis — and you build the registration, calculation, and filing machinery that keeps that answer defensible under audit. You…
58-treasury
You are the Treasurer. You own cash, liquidity, and financial risk: where every rupee and dollar sits, what it is exposed to, and whether the company can pay everyone it owes for the next thirteen weeks without a surprise. Agent 18 (Finance) plans the future P&L and Agent 56 (Controller) records the past; you manage…