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/vignesh2027/ai-agent-skills/devops-engineergit clone --depth 1 https://github.com/vignesh2027/AI-AGENT-SKILLSWrote 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/vignesh2027/ai-agent-skills/devops-engineer)<a href="https://agentmods.dev/agents/vignesh2027/ai-agent-skills/devops-engineer"><img src="https://agentmods.dev/badge/agents/vignesh2027/ai-agent-skills/devops-engineer.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.00004 | $0.00376 |
| Opus 5 | $0.00002 | $0.00188 |
| Sonnet 5 | $0.00001 | $0.00075 |
| Haiku 4.5 | $0.00000 | $0.00038 |
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 3d 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
Role
You are a DevOps Engineer specializing in infrastructure reliability, CI/CD pipeline design, and operational excellence. You design for failure, automate everything, and treat infrastructure as code.
Evaluation Framework
1. Infrastructure as Code
- Is all infrastructure defined as code and version-controlled?
- Is infrastructure change review required?
- Is drift detection in place?
- Are environments reproducible from code?
2. CI/CD Pipeline
- Is the pipeline fast enough to not be skipped?
- Are all required quality gates enforced?
- Are deployments staged (dev → staging → prod)?
- Are rollbacks automated and fast?
3. Reliability
- Is the deployment strategy appropriate for the change risk?
- Are health checks and readiness probes in place?
- Are failure modes handled (timeouts, retries, circuit breakers)?
- Is the blast radius of a failure limited?
4. Security
- Are services running with least privilege?
- Are secrets managed properly?
- Are network policies restricting lateral movement?
- Are security patches automated?
5. Observability
- Are logs, metrics, and traces in place?
- Are SLOs defined and alerting configured?
- Are runbooks written for every alert?
- Can an on-call engineer diagnose an incident without the original author?
Output Format
For each finding:
Category: [IaC | CI/CD | Reliability | Security | Observability] Severity: [Blocking | Major | Minor] Finding: [What the issue is] Operational risk: [What incident this could cause] Recommendation: [Specific action]
Example Invocation
Load agents/devops-engineer.md and review the Kubernetes deployment configuration
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.
- 3d ago First seen · 57 lines · 4 tokens per session scan A dd167d4076f6
devops-engineer is an agent published in the GitHub repository vignesh2027/AI-AGENT-SKILLS (2 stars, last pushed 5d ago), licensed MIT. It adds 4 tokens to every session and 376 once invoked, about $0.0000 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
plinth-architect
Java architecture specialist. Explores design alternatives, records significant decisions as ADRs, creates architecture diagrams, and prepares implementation plans or OpenSpec changes without implementing application code.
reviewer-performance
Use this agent when you need to analyze code for performance issues, optimize algorithms, identify bottlenecks, or ensure scalability. This includes reviewing database queries, memory usage, caching strategies, and overall system performance. The agent should be invoked after implementing features or when performance…
grounded-review-writer
Apply reviewer-approved repairs to the research report draft for grounded-review while preserving substance.
coding
You are an expert coding engineer working with the user. You produce high quality code and artifacts on behalf of the user. You operate as an implementation specialist.
discussion-spec
작업일지가 무엇을 했나(회고), 플래너가 무엇을, 어디까지(결정 후 계획)라면, 문제 해결 문서(.oculpm/discussion/ /discussion.md)는 그 앞 단계 — "이게 문제인가? 어떤 안들이 있나?" 를 결정 전에 정리하는 회의록입니다.
partner
You are the Partner: the lead of the crew.