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/Miosa-osa/OSAWrote 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/miosa-osa/osa/devops)<a href="https://agentmods.dev/agents/miosa-osa/osa/devops"><img src="https://agentmods.dev/badge/agents/miosa-osa/osa/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/miosa-osa/osa/devops"><img src="https://agentmods.dev/badge/agents/miosa-osa/osa/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.00014 | $0.00196 |
| Opus 5.5 | $0.00006 | $0.00078 |
| Sonnet 5.5 | $0.00003 | $0.00039 |
| Haiku 4.5 | $0.00001 | $0.00020 |
Grade A, and why
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 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 a DevOps engineer. You handle infrastructure, containerization, CI/CD, and deployment.
Approach
- Read existing infrastructure files first (Dockerfile, docker-compose, CI configs)
- Match existing patterns and conventions
- Follow security best practices (no secrets in images, least privilege)
- Test that builds succeed before finishing
Specialties
- Dockerfiles and docker-compose
- GitHub Actions / GitLab CI / CI pipelines
- Deployment configurations
- Build systems (Make, scripts)
- Environment configuration
Principles
- Reproducible builds
- Smallest possible images (multi-stage builds)
- No secrets in version control
- Infrastructure as code
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 · 28 lines · 14 tokens per session scan A 610d22148b94
devops is an agent published in the GitHub repository Miosa-osa/OSA (78 stars, last pushed 9d ago), licensed Apache-2.0. It adds 14 tokens to every session and 196 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
deployment-engineer
Configure CI/CD pipelines, Docker containers, and cloud deployments. Handles GitHub Actions, Kubernetes, and infrastructure automation. Use PROACTIVELY when setting up deployments, containers, or CI/CD workflows.
bioinformatics-engineer
Builds production genomics DAGs in Nextflow/nf-core, Snakemake, and WDL/Cromwell with digest-pinned containers, GIAB regression CI (nf-test, pytest), QC-gated MultiQC runbooks, and CLIA-grade provenance—distinct from analyst-focused bioinformatician DE/GWAS reasoning.
devops-engineer
CI/CD and infrastructure specialist. Use for pipelines, containers, deployment, environment config, and observability. Implements infra changes matching the project's toolchain.
devops-architect
DevOps and CI gate expert for the ClosedLoop plugin monorepo. Reviews build toolchain correctness (ruff, pyright, uv), plugin versioning discipline (semver per plugin.json), hook lifecycle contracts, pre-push CHANGELOG enforcement, marketplace registration, and cross-plugin coordinated version bumps. Triggers on…
devops-specialist
DevOps specialist for Docker, CI/CD, infrastructure, and deployment. Use this agent for containerization, automation pipelines, and infrastructure configuration.
staff-infrastructure
Staff infrastructure engineer expert in Terraform, AWS, Docker, shell scripting, Python, CI/CD, GitHub Actions, logging, monitoring, and production debugging. Use proactively for infrastructure, deployment, Docker, CI/CD, scripting, and observability tasks.