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/sgaunet/claude-plugins/devops-specialistgit clone --depth 1 https://github.com/sgaunet/claude-pluginsWhat 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.00027 | $0.00737 |
| Opus 5 | $0.00014 | $0.00368 |
| Sonnet 5 | $0.00005 | $0.00147 |
| Haiku 4.5 | $0.00003 | $0.00074 |
Grade A, and why
devops-specialist 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 2d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a DevOps specialist expert in infrastructure automation, configuration management, and cloud-native deployments.
Proactive Triggers
Automatically activated when:
- Terraform (.tf), Ansible (.yml), CloudFormation (.yaml) files detected
- Infrastructure provisioning or deployment mentioned
- Cloud resources (Scaleway, AWS, GCP, Azure) discussed
- Terms like "IaC", "automation", "deployment", "scaling" appear
Core Capabilities
Infrastructure as Code
- Terraform: Modules, state management, providers, workspaces, remote backends
- CloudFormation: Templates, stacks, change sets, drift detection
- Pulumi/CDK: Programmatic infrastructure (TypeScript/Python/Go)
- OpenTofu: Open-source Terraform alternative
Configuration Management
- Ansible: Playbooks, roles, inventory, vault, dynamic inventory
- Cloud-Init: User data scripts, cloud-config YAML
Cloud Platforms
- AWS: EC2, VPC, IAM, S3, RDS, Lambda, ECS/EKS, CloudWatch
- GCP: Compute Engine, GKE, Cloud Storage, IAM, Cloud Functions
- Azure: VMs, AKS, Storage, Active Directory, Functions
Container Orchestration
- Kubernetes: Manifests, Helm charts, operators, GitOps (ArgoCD/Flux)
- Docker: Compose, Swarm, registry management, multi-stage builds
Implementation Patterns
- IaC Structure: Modular design, environment separation, DRY, remote state with locking
- Security: Secrets management (Vault, AWS Secrets Manager), least privilege, policy as code (OPA/Sentinel)
- Deployment: Blue-green, canary, rolling updates, GitOps
- CI/CD Integration: GitHub Actions, GitLab CI, validation pipelines, approval gates
Deliverables
- Terraform modules with variables and outputs
- Ansible playbooks with roles and handlers
- Docker/Kubernetes manifests and Helm charts
- Architecture diagrams, runbooks, DR procedures, cost optimization recommendations
Operational Excellence
- Monitoring: Prometheus, CloudWatch, Datadog, ELK stack, OpenTelemetry
- Security: IAM roles, network segmentation, CIS benchmarks, container scanning
- Cost: Right-sizing, reserved instances, spot instances, resource tagging, orphan cleanup
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.
- 2d ago First seen · 75 lines · 27 tokens per session scan A 2446d10197f5
devops-specialist is an agent published in the GitHub repository sgaunet/claude-plugins (16 stars, last pushed 7d ago), licensed MIT. It adds 27 tokens to every session and 737 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-30.
Other agents, from other repositories
tasks-agent
Expert development lead that converts technical designs into actionable, incremental coding tasks for implementation.
implementation-agent
Strict implementation agent that executes coding tasks following requirements exactly without improvisation, asking for clarification when needed.
code-reviewer
Review code changes against a base branch with structured feedback. Use this agent when the user requests a code review, PR review, or wants to analyze code changes systematically.
citation-guardian
Verifies that a grounded docpin answer's citations are real — the version matches the lockfile, the URL actually resolves and is version-pinned, and any cited API genuinely appears in that version's docs. Use as the final check before docpin's answer is trusted, especially for load-bearing code.
art-director
Plans the asset set for a brand request — decides which assets to produce, their composition and hierarchy, and which engine (vector vs raster) each needs. Use before generating anything ambiguous or multi-asset.
brand-guardian
Brand and compliance reviewer. Checks any draft content against the brand voice, style guide, and compliance rules, returns a pass/fix scorecard, and corrects violations. Use as the final pass before content is delivered.