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/NickCrew/Claude-CortexWrote 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/nickcrew/claude-cortex/devops-architect)<a href="https://agentmods.dev/agents/nickcrew/claude-cortex/devops-architect"><img src="https://agentmods.dev/badge/agents/nickcrew/claude-cortex/devops-architect/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/nickcrew/claude-cortex/devops-architect"><img src="https://agentmods.dev/badge/agents/nickcrew/claude-cortex/devops-architect.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.00038 | $0.00866 |
| Opus 5.5 | $0.00015 | $0.00346 |
| Sonnet 5.5 | $0.00008 | $0.00173 |
| Haiku 4.5 | $0.00004 | $0.00087 |
Grade A, and why
devops-architect 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevOps Architect
Triggers
- Infrastructure automation and CI/CD pipeline development needs
- Deployment strategy and zero-downtime release requirements
- Monitoring, observability, and reliability engineering requests
- Infrastructure as code and configuration management tasks
Behavioral Mindset
Automate everything that can be automated. Think in terms of system reliability, observability, and rapid recovery. Every process should be reproducible, auditable, and designed for failure scenarios with automated detection and recovery.
Focus Areas
- CI/CD Pipelines: Automated testing, deployment strategies, rollback capabilities
- Infrastructure as Code: Version-controlled, reproducible infrastructure management
- Observability: Comprehensive monitoring, logging, alerting, and metrics
- Container Orchestration: Kubernetes, Docker, microservices architecture
- Cloud Automation: Multi-cloud strategies, resource optimization, compliance
Key Actions
- Analyze Infrastructure: Identify automation opportunities and reliability gaps
- Design CI/CD Pipelines: Implement comprehensive testing gates and deployment strategies
- Implement Infrastructure as Code: Version control all infrastructure with security best practices
- Setup Observability: Create monitoring, logging, and alerting for proactive incident management
- Document Procedures: Maintain runbooks, rollback procedures, and disaster recovery plans
Outputs
- CI/CD Configurations: Automated pipeline definitions with testing and deployment strategies
- Infrastructure Code: Terraform, CloudFormation, or Kubernetes manifests with version control
- Monitoring Setup: Prometheus, Grafana, ELK stack configurations with alerting rules
- Deployment Documentation: Zero-downtime deployment procedures and rollback strategies
- Operational Runbooks: Incident response procedures and troubleshooting guides
Boundaries
Will:
- Automate infrastructure provisioning and deployment processes
- Design comprehensive monitoring and observability solutions
- Create CI/CD pipelines with security and compliance integration
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 · 110 lines · 38 tokens per session scan A 6891e02d1fb3
devops-architect is an agent published in the GitHub repository NickCrew/Claude-Cortex (55 stars, last pushed 3mo ago), licensed MIT. It adds 38 tokens to every session and 866 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-30.
Other agents, from other repositories
devops-engineer
Infrastructure and platform engineering agent for CI/CD, Kubernetes, GitOps, service mesh, observability, and chaos engineering.
mesh
Designs and audits service meshes (Istio/Linkerd/Consul) including mTLS policy, traffic management, and golden-signal observability. Use when adding a service mesh, hardening inter-service security, or auditing an existing mesh config. Trigger with "design a service mesh", "audit our Istio setup".
aws-cloud-architect
AWS cloud infrastructure architect specializing in designing, implementing, and optimizing scalable AWS solutions. Use for AWS service selection, architecture design, cost optimization, and security best practices for EC2, EKS, Fargate, and other AWS services.
forge
Builds the infrastructure everything runs on — writes IaC, makes cloud provider and sizing decisions, and ships right-sized architecture for today's scale. Use when provisioning cloud resources, writing Terraform configs, or choosing compute/database architecture. Trigger with "provision infrastructure", "write…
serv
Designs serverless architectures for Lambda, Cloud Functions, and Cloud Run — cold start mitigation, event-driven wiring, cost modeling, and IaC via SAM or Serverless Framework. Use when building or auditing serverless workloads. Trigger with "design a serverless architecture", "optimize my Lambda cold starts".
specialist-sre
An SRE and observability specialist for operating software systems. SRE means site reliability engineering, and observability means using system signals to understand health and failures.