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 skills/giggsoinc/raven/devops-specialistnpx skills add giggsoinc/raven --skill devops-specialistgit clone --depth 1 https://github.com/giggsoinc/ravenWrote 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/giggsoinc/raven/devops-specialist)<a href="https://agentmods.dev/skills/giggsoinc/raven/devops-specialist"><img src="https://agentmods.dev/badge/skills/giggsoinc/raven/devops-specialist.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.00040 | $0.00944 |
| Opus 5 | $0.00020 | $0.00472 |
| Sonnet 5 | $0.00008 | $0.00189 |
| Haiku 4.5 | $0.00004 | $0.00094 |
Grade A, and why
devops-specialist scanned grade A with 1 finding 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 5d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **Health checks:** service-specific (pg_isready, redis-cli ping, curl /health), not just container running How it starts
The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevOps / SRE Specialist — Kelsey Hightower (SRE, Google)
Assumed Expert
Kelsey Hightower (SRE, Google) Explaining as a senior engineer teaching someone who knows adjacent tech but is new to DevOps / SRE.
Core Focus
CI/CD, observability, SLOs, incident response, deployment strategies, toil reduction, docker-compose local dev, container orchestration
Local Dev with Docker-Compose
Most projects start local before hitting K8s. Docker-compose is the local dev standard.
Patterns
- Multi-service stack: API + DB + cache + queue — one
docker-compose up - GPU workloads:
deploy.resources.reservations.deviceswithdriver: nvidia - ML stacks: model-server + feature-store + vector-db + API gateway + monitoring
- Data stacks: postgres + redis + kafka + airflow — compose profiles for optional services
- Volume strategy: mount code for hot-reload, named volumes for data persistence, never bake data into images
- Health checks: service-specific (pg_isready, redis-cli ping, curl /health), not just container running
- Networking: use service names as hostnames, custom networks for isolation, expose only what's needed
Docker-Compose vs Docker vs K8s Decision
| Signal | → Use |
|---|---|
| Local dev, single developer | Docker-compose |
| CI pipeline, single container | Docker (plain) |
| Multi-container local dev | Docker-compose |
| Multi-container staging/prod | K8s (or K3s for small) |
| GPU local dev (ML) | Docker-compose with nvidia runtime |
| GPU production | K8s with GPU node pools |
| "Do I need K8s?" | If < 5 services and < 3 developers → no |
Gotchas
depends_ononly waits for container start, NOT for service ready — use health checks.envfile loading order matters — explicitenv_file:beats implicit.env- Docker Desktop resource limits — default 2GB RAM kills multi-service stacks
- Compose V2 (
docker compose) vs V1 (docker-compose) — V2 is the standard, V1 is deprecated - Bind mounts on macOS are SLOW for node_modules — use named volume or mutagen
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.
- 5d ago First seen · 102 lines · 40 tokens per session scan A 94e9c77f0e80
devops-specialist is a skill published in the GitHub repository giggsoinc/raven (5 stars, last pushed 4d ago), licensed MIT. It adds 40 tokens to every session and 944 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…