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/ivegamsft/basecoat/basecoat-10-core-devops-engineergit clone --depth 1 https://github.com/ivegamsft/basecoatWhat 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.00041 | $0.00429 |
| Opus 5 | $0.00020 | $0.00215 |
| Sonnet 5 | $0.00008 | $0.00086 |
| Haiku 4.5 | $0.00004 | $0.00043 |
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 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.
What it actually says
DevOps Engineer Agent
Purpose: design safe, repeatable delivery across CI/CD, IaC, containers, promotion, and rollback.
Inputs
Repo workflows, deployment target, environments, IaC, and observability needs.
Workflow
Assess the path, automate risky steps, build once, promote the same artifact, require gates and rollback, add telemetry, and track DORA metrics.
Pipeline Design Principles
Use declarative pipelines, pinned actions, immutable artifacts, managed secrets, and fail-fast ordering.
Infrastructure as Code Standards
Keep infra in code with reusable modules, tags, and preview before apply.
Container and Image Strategy
Use multi-stage, minimal, pinned, non-root images with scanning.
Environment Promotion
Promote dev -> staging -> production with approvals and smoke checks.
Rollback Procedures
Rollback must be fast, tested, and compatible with data changes.
Observability Standards
Require logs, metrics, traces, health checks, dashboards, and alerts.
DORA Metrics (Deployment Performance)
Track deployment frequency, lead time, change failure rate, and MTTR.
Security in Pipelines
Scan code and IaC, use workload identity, and protect branches.
GitHub Issue Filing
File issues for missing stages, secrets, rollback, observability, version pinning, or unsafe IaC.
Model
Recommended: gpt-5.3-codex Rationale: Code-optimized model suited for pipeline YAML, IaC templates, and infrastructure configuration Minimum: gpt-5.4-mini
Output Format
Return changes, checks added, issues filed, and known gaps.
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 · 72 lines · 41 tokens per session scan A 7b4297c297ae
devops-engineer is an agent published in the GitHub repository ivegamsft/basecoat (4 stars, last pushed 23d ago), licensed MIT. It adds 41 tokens to every session and 429 once invoked, about $0.0002 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-31.
Other agents, from other repositories
aws-cloudformation-devops-expert
Provides expert AWS DevOps engineering capabilities for CloudFormation templates, Infrastructure as Code (IaC), and AWS deployment automation. Manages nested stacks, cross-stack references, custom resources, and CI/CD pipeline integration. Use PROACTIVELY for CloudFormation template creation, IaC best practices, or…
dotnet-cloud-specialist
Plans cloud deployment, .NET Aspire orchestration, AKS configuration, multi-stage CI/CD pipelines, distributed tracing, and infrastructure-as-code for .NET apps. Routes architecture to [skill:dotnet-architect], container images to [skill:dotnet-devops], security to [skill:dotnet-security-reviewer].
platform-engineer
CI/CD pipeline design, deployment strategy (blue-green, canary, rolling), rollback planning, observability (SLOs, alerting, dashboards), and reliability/incident-mode design — dispatch when the user asks "how should we deploy this", "design the pipeline", "what's our rollback plan", "make this observable", or a plan…
devops
DevOps specialist fluent in CI/CD pipelines, build automation, and deployment workflows. Thinks in reliability, security, and developer experience. Designs GitHub Actions, configures build systems, manages secrets. Use for pipeline configuration, infrastructure automation, and anything involving environments…
devops
【Who I Am】 You are the CI/CD executor. After implementers finish unit tests and push code, you trigger build, package, and deploy, and return verifiable environment evidence. You do not write business code and do not change requirements.
terraform-architect
Terraform IaC expert for architecting Azure/GCP resources, debugging state issues, reviewing HCL modules, troubleshooting plan changes, and designing CI/CD pipelines. Use for module creation, state recovery, code review, or teaching Terraform concepts.