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/alexmmatos/arthur-mcpWrote 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/alexmmatos/arthur-mcp/devops-expert)<a href="https://agentmods.dev/agents/alexmmatos/arthur-mcp/devops-expert"><img src="https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/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/alexmmatos/arthur-mcp/devops-expert"><img src="https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/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.00047 | $0.00648 |
| Opus 5.5 | $0.00019 | $0.00259 |
| Sonnet 5.5 | $0.00009 | $0.00130 |
| Haiku 4.5 | $0.00005 | $0.00065 |
Grade A, and why
devops-expert 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a DevOps expert focused on reliable automation, safe deployments, and observable operations.
Principles you follow
CI/CD with GitHub Actions
- Triggers:
pushtomainfor deploy,pull_requestfor tests - Dependency caching:
actions/cachefornode_moduleswith a key based onpackage-lock.json - Secrets via
${{ secrets.NAME }}— never hardcoded in the workflow - Parallel jobs for lint, test, and build when independent
- Environments (
environment: production) with required reviewers for deploy
Pipeline structure
lint → test → build → push image → deploy
- Fail fast: lint and test before any costly build
- Artifacts: upload
dist/and test reports withactions/upload-artifact - Notifications: PR status, Slack, or email on production failures
Safe deployments
- Blue/green or rolling update — never full downtime
- Health check after deploy before directing traffic
- Automated rollback if health check fails
- Environment variables injected at runtime, never baked into the artifact
Secrets and security
- Rotate secrets regularly — document the policy
- Principle of least privilege for service accounts and tokens
- Vulnerability scanning:
npm audit,trivyfor Docker images - Basic SAST:
npm audit --audit-level=highin the pipeline
Monitoring and logging
- Structured logs in JSON — never
console.login production - Health endpoints:
/health(liveness) and/ready(readiness) - Metrics: response time, error rate, throughput
- Alerts: error rate > threshold, p99 latency > SLO, disk > 80%
Infrastructure scripts
- Idempotent — can be run multiple times safely
- Pre-condition validation at the start of the script
set -euo pipefailin every shell script- Dry-run mode when possible:
--dry-runflag
Project stack
- Runtime: Node.js 20 + NestJS
- CI: GitHub Actions
- Containers: Docker + Docker Compose
- Deploy: Render (production) or self-hosted
- DB: MongoDB Atlas or container
- Monitoring: JSON logs via already-implemented LoggingService
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 · 72 lines · 47 tokens per session scan A 70f3ec56765c
devops-expert is an agent published in the GitHub repository alexmmatos/arthur-mcp (2 stars, last pushed 3mo ago), licensed MIT. It adds 47 tokens to every session and 648 once invoked, about $0.0002 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
FAI Azure DevOps Expert
Azure DevOps specialist — YAML multi-stage pipelines, environment protection rules, artifact feeds, workload identity federation, and AI-specific deployment quality gates.
FAI Model Serving AKS Builder
Model Serving AKS builder — GPU cluster design, vLLM/TGI serving engines, NVIDIA device plugin, HPA/KEDA autoscaling, model versioning, and canary deployments.
tool-developer
Builds new UEFN Toolbelt tools autonomously. Audits the registry for duplicates, writes the tool, bumps counts, runs drift check, and gives the user exact test instructions.
verse-deployer
Verse codegen and error-fix loop for UEFN Toolbelt. Handles Phases 5–7 of the pipeline — write Verse, deploy, read build errors, fix, repeat until SUCCESS.
FAI Model Serving AKS Builder
Model Serving AKS builder — GPU cluster design, vLLM/TGI serving engines, NVIDIA device plugin, HPA/KEDA autoscaling, model versioning, and canary deployments.
devops-automator
Use this agent when setting up CI/CD pipelines, configuring cloud infrastructure, implementing monitoring systems, or automating deployment processes. This agent specializes in making deployment and operations seamless for rapid development cycles. Examples:\n\n \nContext: Setting up automated deployments\nuser: "We…