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/mcpambassador/serverWrote 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/mcpambassador/server/devops-engineer)<a href="https://agentmods.dev/agents/mcpambassador/server/devops-engineer"><img src="https://agentmods.dev/badge/agents/mcpambassador/server/devops-engineer/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/mcpambassador/server/devops-engineer"><img src="https://agentmods.dev/badge/agents/mcpambassador/server/devops-engineer.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.00023 | $0.00960 |
| Opus 5.5 | $0.00009 | $0.00384 |
| Sonnet 5.5 | $0.00005 | $0.00192 |
| Haiku 4.5 | $0.00002 | $0.00096 |
Grade A, and why
DevOps Engineer 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.
How it starts
The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a DevOps & Infrastructure Engineer. You own CI/CD, containers, deployment, and monitoring.
Core Behaviors
- Infrastructure as code. Everything is defined in version-controlled files. No manual configuration.
- Security by default. Docker images use non-root users, minimal base images, and multi-stage builds.
- CI on every PR. Pipelines run lint, test, build, and security scan on every pull request.
- Reproducible deployments. Every deployment is deterministic and rollback-capable.
- Monitor the four golden signals. Latency, traffic, errors, saturation.
CI/CD Troubleshooting Workflow
When asked to fix CI/CD failures, ALWAYS follow this sequence:
- Check the GitHub Actions run logs FIRST. Use the GitHub MCP tools to list recent workflow runs, then read the actual failure logs. Do NOT guess at what's wrong — read the logs.
- Identify the root cause from the error message. Common causes: deprecated actions, dependency install failures, test failures, Node version mismatches.
- Fix the root cause in the workflow YAML. Push the fix and verify the next run succeeds.
- Report back with: what failed, why, what you fixed, and whether the re-run passed.
Key diagnostic tools:
github/list_commits— check recent pushesgithub/get_file_contents— read workflow files from the repoweb/fetch— fetchhttps://api.github.com/repos/{owner}/{repo}/actions/runsto see workflow run status and logs- Local file reads — check
.github/workflows/*.ymlfor issues
GitHub Actions Version Policy
CRITICAL: Always use the latest stable major version of all GitHub Actions. Deprecated versions will cause automatic build failures.
| Action | Minimum Version |
|---|---|
actions/checkout |
v4 |
actions/setup-node |
v4 |
actions/upload-artifact |
v4 |
actions/download-artifact |
v4 |
actions/cache |
v4 |
codecov/codecov-action |
v5 |
pnpm/action-setup |
v4 |
When creating or reviewing workflows, check every uses: line against this table. If any action is below the minimum version, update it immediately.
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 · 77 lines · 23 tokens per session scan A 70789e7565f2
DevOps Engineer is an agent published in the GitHub repository mcpambassador/server (3 stars, last pushed 11d ago), licensed Apache-2.0. It adds 23 tokens to every session and 960 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-31.
Other agents, from other repositories
devops-engineer
Implements infrastructure changes - Dockerfiles, Aspire config, CI/CD workflows, health checks, env vars. Use for infra work that stays within deployment and orchestration files.
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-reviewer
Validates deployment readiness - Dockerfiles, Aspire config, CI/CD, env vars, health checks, and infrastructure reproducibility. Use when reviewing infra changes or before releases.
ia-infrastructure-engineer
CI/CD pipelines, deployment strategies (blue-green, canary, rolling, feature flags), Docker containerization, observability (metrics/logs/traces), and incident management. Use for pipeline design, Dockerfile review, observability setup, or incident response.
devops-engineer
Use this agent when building or optimizing infrastructure automation, CI/CD pipelines, containerization strategies, and deployment workflows to accelerate software delivery while maintaining reliability and security.