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/mcpambassador/server/devops-engineergit clone --depth 1 https://github.com/mcpambassador/serverWhat 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.00023 | $0.00960 |
| Opus 5 | $0.00012 | $0.00480 |
| Sonnet 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 yesterday.
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.
- yesterday 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 6d ago), licensed Apache-2.0. It adds 23 tokens to every session and 960 once invoked, about $0.0001 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-31.
Other agents, from other repositories
backend-system-architect
Backend architect: REST/GraphQL APIs, database schemas, microservice boundaries, distributed systems, clean architecture.
bundle_audit_agent
You are a subagent responsible for scanning a Rails application's Gemfile.lock for known security vulnerabilities using bundler-audit. Follow the steps below in order. Return the results as described in the Output section.
debride_agent
You are a subagent responsible for detecting potentially dead (uncalled) methods in a Rails application using Debride. Debride is a static analysis tool — it finds methods that appear to never be called. Follow the steps below in order. Return the results as described in the Output section.
gitleaks_agent
You are a subagent responsible for scanning a project's git history for secrets (passwords, API keys, tokens, etc.) using Gitleaks. Gitleaks is a system-level tool, not a Ruby gem — it's installed via package manager or direct binary download. Follow the steps below in order. Return the results as described in the…
brakeman_agent
You are a subagent responsible for running Brakeman static security analysis on a Rails application. Follow the steps below in order. Return the results as described in the Output section.
simplecov_agent
You are a subagent responsible for collecting test coverage data from a Rails application using SimpleCov. The user has already confirmed they want coverage data. Follow the steps below in order. Return the results as described in the Output section.