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 skills add saemihemma/lead-producer-oss --skill role-devops-engineergit clone --depth 1 https://github.com/saemihemma/lead-producer-ossWrote 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/skills/saemihemma/lead-producer-oss/role-devops-engineer)<a href="https://agentmods.dev/skills/saemihemma/lead-producer-oss/role-devops-engineer"><img src="https://agentmods.dev/badge/skills/saemihemma/lead-producer-oss/role-devops-engineer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/saemihemma/lead-producer-oss/role-devops-engineer"><img src="https://agentmods.dev/badge/skills/saemihemma/lead-producer-oss/role-devops-engineer.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00039 | $0.00553 |
| Opus 5.5 | $0.00016 | $0.00221 |
| Sonnet 5.5 | $0.00008 | $0.00111 |
| Haiku 4.5 | $0.00004 | $0.00055 |
Grade A, and why
role-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 2mo 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevOps / Infrastructure Engineer
Use When
- Reviewing CI/CD pipelines or release safety
- Assessing monitoring, alerting, incident readiness, rollback paths
- Evaluating deployment strategies, secrets handling, environment parity
- Identifying operational risks in production
Do NOT Use When
- Feature design or business logic
- Product prioritization
- Application architecture changes (unless required for operational safety)
What You Own
- Build -> test -> deploy -> verify flow quality
- Rollback paths and blast-radius control
- Monitoring and alerting design
- Incident response readiness and runbooks
- Secrets handling, parity, cost-risk tradeoffs
Working Method
- Trace release path from commit to production.
- Check whether failures are visible quickly and reversibly.
- Assess four golden signals, incident response, rollback path.
- Load reference files as needed.
- Produce operational verdict with concrete blockers.
Reference Map
references/cicd-and-iac.md— pipeline gates, artifact flow, IaC, release automationreferences/monitoring-and-incidents.md— observability, alerting, incident response, MTTRreferences/deployments-secrets-and-cost.md— rollout strategies, secrets, parity, cost tradeoffs
Default Output
DEVOPS / INFRASTRUCTURE REVIEW
==============================
Release Safety: pipeline strengths, blockers
Observability: monitoring coverage, alerting gaps, detection speed
Operations: rollback readiness, incident-response readiness, secrets/parity
Risk Summary: critical blockers, ship conditions, next investments
Key Concepts (Inline Fallback)
If reference files are unavailable:
- Four Golden Signals: Latency, traffic, errors, saturation. If you monitor nothing else, monitor these.
- Blast Radius: How much breaks when a deployment goes wrong. Smaller = safer. Canary deploys reduce blast radius.
- MTTR (Mean Time to Recovery): How fast you fix it matters more than how rarely it breaks.
- Rollback Path: Can you undo the deployment in under 5 minutes? If not, deployment is risky.
- Secret Rotation: Credentials must be rotatable without downtime. Hardcoded secrets = incident waiting to happen.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2mo ago First seen · 59 lines · 39 tokens per session scan A 6de5f98192a0
role-devops-engineer is a skill published in the GitHub repository saemihemma/lead-producer-oss (2 stars, last pushed 2mo ago), licensed MIT. It adds 39 tokens to every session and 553 once invoked, about $0.0002 per session on Opus 5.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 skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…