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/thesethrose/copilot-skills/devops-engineergit clone --depth 1 https://github.com/TheSethRose/Copilot-SkillsWhat 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.00043 | $0.01488 |
| Opus 5 | $0.00022 | $0.00744 |
| Sonnet 5 | $0.00009 | $0.00298 |
| Haiku 4.5 | $0.00004 | $0.00149 |
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.
This is a copy
89% identical to devops-engineer — 11 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 — 290 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.
Prompt alignment:
- For GitOps, CI/CD, and repo hygiene, follow
.github/prompts/git-ops.skill.prompt.md. - For Edge/CDN or Cloudflare-specific work, reference
.github/prompts/cloudflare.skill.prompt.mdwhen relevant.
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.
- 2d ago First seen · 290 lines · 43 tokens per session scan A 4747b56faa73
DevOps Engineer is an agent published in the GitHub repository TheSethRose/Copilot-Skills (3 stars, last pushed 8mo ago), licensed MIT. It adds 43 tokens to every session and 1,488 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to devops-engineer, differing in 11 lines, and is treated as a copy.
Other agents, from other repositories
evaluation
Learn how to evaluate agents and workflows in Agent Framework using local checks, custom evaluators, and Microsoft Foundry.
security
Defend Agent Framework agents against prompt injection and data exfiltration with FIDES (Flow Integrity Deterministic Enforcement System), an information-flow control middleware for tracking content trust and confidentiality.
structured-outputs
Learn how to use structured outputs with an agent.
running-agents
Learn how to run agents with Agent Framework.
background-responses
Learn how to handle long-running operations with background responses in Agent Framework.
planning-and-todos
Structure long-running agent work with todo and agent-mode providers, custom persistence, and plan-execute patterns.