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/monkilabs/opencastleWrote 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/monkilabs/opencastle/devops-expert)<a href="https://agentmods.dev/agents/monkilabs/opencastle/devops-expert"><img src="https://agentmods.dev/badge/agents/monkilabs/opencastle/devops-expert/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/monkilabs/opencastle/devops-expert"><img src="https://agentmods.dev/badge/agents/monkilabs/opencastle/devops-expert.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.00035 | $0.00674 |
| Opus 5.5 | $0.00014 | $0.00270 |
| Sonnet 5.5 | $0.00007 | $0.00135 |
| Haiku 4.5 | $0.00003 | $0.00067 |
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 9d 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.
DevOps Expert
Deployments, CI/CD, cron jobs, security headers, caching, environment variables, pre-release verification, changelogs.
Skills
Resolve skills (slots, direct) via .opencastle/agents/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.
- 9d ago Changed · -3 lines c5b55f74d3b6
- 11d ago Changed 647deffea153
- 1mo ago First seen · 55 lines · 35 tokens per session scan A ff86315758fc
DevOps & Release is an agent published in the GitHub repository monkilabs/opencastle (80 stars, last pushed yesterday), licensed MIT. It adds 35 tokens to every session and 674 once invoked, about $0.0001 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
GitHub Actions Node Runtime Upgrade
Upgrade a GitHub Actions JavaScript/TypeScript action to a newer Node runtime version (e.g., node20 to node24) with major version bump, CI updates, and full validation.
aidlc-pipeline-deploy-agent
CI/CD engineer and release manager responsible for pipeline configuration, deployment strategy, and release execution. Leads Practices Discovery, CI Pipeline, Deployment Pipeline, and Deployment Execution stages.
shipper
Release Lifecycle & Deploy Intelligence Agent (Leo Andersen) - Pre-deploy checklist, changelog, version tagging, smoke test, rollback.
bt6-release-integrator
Runs conservative one-at-a-time merge trains for BT6 repositories with CI, evidence, compatibility, and issue reconciliation gates.
build-engineer
Owns build automation, CI reliability, packaging, and artifact discipline.
dev-devops
Guardião de DevOps e releases. Autoridade EXCLUSIVA para git push, gh pr create/merge, CI/CD e releases. Use SOMENTE para subir código, abrir PRs, gerenciar releases e operações de infraestrutura.