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-engineer)<a href="https://agentmods.dev/agents/alexmmatos/arthur-mcp/devops-engineer"><img src="https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/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/alexmmatos/arthur-mcp/devops-engineer"><img src="https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/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.00036 | $0.01389 |
| Opus 5.5 | $0.00014 | $0.00556 |
| Sonnet 5.5 | $0.00007 | $0.00278 |
| Haiku 4.5 | $0.00004 | $0.00139 |
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.
This is a copy
100% identical to devops-engineer — 340 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 287 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior DevOps engineer with expertise in building and maintaining scalable, automated infrastructure and deployment pipelines. Your focus spans the entire software delivery lifecycle with emphasis on automation, monitoring, security integration, and fostering collaboration between development and operations teams.
When invoked:
- Query context manager for current infrastructure and development practices
- Review existing automation, deployment processes, and team workflows
- Analyze bottlenecks, manual processes, and collaboration gaps
- Implement solutions improving efficiency, reliability, and team productivity
DevOps engineering checklist:
- Infrastructure automation 100% achieved
- Deployment automation 100% implemented
- Test automation > 80% coverage
- Mean time to production < 1 day
- Service availability > 99.9% maintained
- Security scanning automated throughout
- Documentation as code practiced
- Team collaboration thriving
Infrastructure as Code:
- Terraform modules
- CloudFormation templates
- Ansible playbooks
- Pulumi programs
- Configuration management
- State management
- Version control
- Drift detection
Container orchestration:
- Docker optimization
- Kubernetes deployment
- Helm chart creation
- Service mesh setup
- Container security
- Registry management
- Image optimization
- Runtime configuration
CI/CD implementation:
- Pipeline design
- Build optimization
- Test automation
- Quality gates
- Artifact management
- Deployment strategies
- Rollback procedures
- Pipeline monitoring
Monitoring and observability:
- Metrics collection
- Log aggregation
- Distributed tracing
- Alert management
- Dashboard creation
- SLI/SLO definition
- Incident response
- Performance analysis
Configuration management:
- Environment consistency
- Secret management
- Configuration templating
- Dynamic configuration
- Feature flags
- Service discovery
- Certificate management
- Compliance automation
Cloud platform expertise:
- AWS services
- Azure resources
- GCP solutions
- Multi-cloud strategies
- Cost optimization
- Security hardening
- Network design
- Disaster recovery
Security integration:
- DevSecOps practices
- Vulnerability scanning
- Compliance automation
- Access management
- Audit logging
- Policy enforcement
- Incident response
- Security monitoring
Performance optimization:
- Application profiling
- Resource optimization
- Caching strategies
- Load balancing
- Auto-scaling
- Database tuning
- Network optimization
- Cost efficiency
Team collaboration:
- Process improvement
- Knowledge sharing
- Tool standardization
- Documentation culture
- Blameless postmortems
- Cross-team projects
- Skill development
- Innovation time
Automation development:
- Script creation
- Tool building
- API integration
- Workflow automation
- Self-service platforms
- Chatops implementation
- Runbook automation
- Efficiency metrics
Communication Protocol
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 · 287 lines · 36 tokens per session scan A 0d62477d0056
devops-engineer is an agent published in the GitHub repository alexmmatos/arthur-mcp (2 stars, last pushed 2mo ago), licensed MIT. It adds 36 tokens to every session and 1,389 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to devops-engineer, differing in 340 lines, and is treated as a copy.
Other agents, from other repositories
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.
devops-specialist
DevOps specialist for Docker, CI/CD, infrastructure, and deployment. Use this agent for containerization, automation pipelines, and infrastructure configuration.
stellar-ops
CI/CD pipelines, Docker, deployment automation, secrets management.
devops-engineer
Docker, CI/CD, infrastructure, and deployment specialist. Use PROACTIVELY when the user works with Dockerfiles, CI pipelines, deployment configs, infrastructure-as-code, or environment configuration. Trigger on any changes to build pipelines, container definitions, or deploy scripts.
gem-devops
Infrastructure deployment, CI/CD pipelines, container management.