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/superclaude-org/superclaude_plugin/sc-devops-architectgit clone --depth 1 https://github.com/SuperClaude-Org/SuperClaude_PluginWrote 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/superclaude-org/superclaude_plugin/sc-devops-architect)<a href="https://agentmods.dev/agents/superclaude-org/superclaude_plugin/sc-devops-architect"><img src="https://agentmods.dev/badge/agents/superclaude-org/superclaude_plugin/sc-devops-architect.svg" alt="Measured on agentmods" 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 | $0.00019 | $0.00466 |
| Opus 5 | $0.00010 | $0.00233 |
| Sonnet 5 | $0.00004 | $0.00093 |
| Haiku 4.5 | $0.00002 | $0.00047 |
Grade A, and why
sc-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 4d 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
98% identical to devops-architect — 2 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 — 49 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.
- 4d ago First seen · 49 lines · 19 tokens per session scan A 1f83a22ba257
sc-devops-architect is an agent published in the GitHub repository SuperClaude-Org/SuperClaude_Plugin (55 stars, last pushed 13d ago), licensed MIT. It adds 19 tokens to every session and 466 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 98% identical to devops-architect, differing in 2 lines, and is treated as a copy.
Other agents, from other repositories
repo-research-analyst
Note: The current year is 2026. Use this when searching for recent documentation and patterns.
slack-researcher
Note: The current year is 2026. Use this when assessing the recency of Slack discussions.
web-researcher
Note: The current year is 2026. Use this when assessing the recency and relevance of external sources.
data-migration-reviewer
You are a data migration and schema-change reviewer. Evaluate planned or existing migration work for three layers, in order.
pr-comment-resolver
You implement one PR review fix that the orchestrator has already judged valid and worth doing. Your job is to implement it well and return a structured summary -- not to re-litigate whether it was worth fixing. The legitimacy gate already happened in the context that could see every thread at once; you have a…
media-analyzer
You are a media-analysis specialist inside an already-running ce-sweep pass. You receive one feedback item that has media attached, turn its downloaded frames and transcript into a single bug-report-shaped finding, write that finding to a scratch artifact, and return a compact pointer. You do not fix anything and you…