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/xobotyi/cc-foundry/devopsnpx skills add xobotyi/cc-foundry --skill devopsgit clone --depth 1 https://github.com/xobotyi/cc-foundryWhat 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.00067 | $0.03855 |
| Opus 5 | $0.00034 | $0.01928 |
| Sonnet 5 | $0.00013 | $0.00771 |
| Haiku 4.5 | $0.00007 | $0.00385 |
Grade A, and why
devops 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Good: `systemctl restart caddy && curl -f http://localhost:80/health` How it starts
The opening of the file, as written. The whole thing — 336 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevOps Discipline
Declarative, reproducible, observable, secure by default.
Every infrastructure failure traces to one of four root causes:
- Undeclared state — infrastructure exists that isn't in code
- Unverified changes — changes deployed without testing or rollback plan
- Invisible systems — infrastructure that can't be monitored or debugged
- Assumed security — security treated as a later hardening step instead of a default
This skill prevents all four.
References
- IaC principles — [
${CLAUDE_SKILL_DIR}/references/iac-principles.md]: GitOps v1.0 spec, 12-factor methodology, state management comparison (stateful/stateless/GitOps), configuration design patterns, IaC maturity data - Observability — [
${CLAUDE_SKILL_DIR}/references/observability.md]: Three pillars deep dive, SLI/SLO/error budget framework, DORA metrics, toil reduction patterns, common observability gaps, sampling strategies - Change management — [
${CLAUDE_SKILL_DIR}/references/change-management.md]: Deployment strategy comparison table, release engineering principles, rollback requirements checklist, progressive delivery tooling - Security posture — [
${CLAUDE_SKILL_DIR}/references/security-posture.md]: Zero trust NIST domains, JIT access patterns, certificate lifecycle, machine identity governance, supply chain integrity, policy-as-code tooling - Disaster recovery — [
${CLAUDE_SKILL_DIR}/references/disaster-recovery.md]: RTO/RPO sizing by business impact, service tiering, recovery architecture trade-offs, chaos engineering approaches and tooling - Testing — [
${CLAUDE_SKILL_DIR}/references/testing.md]: Testing pyramid layers with tool lists, IaC quality metrics, runbook format and automation maturity levels, incident response patterns
Core Principles
These apply to all infrastructure work regardless of tool.
Everything in Code
- All infrastructure is defined in version-controlled, declarative code
- No manual changes through CLI, console, or SSH. If it's not in code, it doesn't exist
- Configuration is separated from code — config varies between environments, code does not
- Changes go through code review before deployment
- Every change is auditable: who changed what, when, why
What ships with it
7 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.
- 2d ago First seen · 336 lines · 67 tokens per session scan A e53d7002a12c
devops is a skill published in the GitHub repository xobotyi/cc-foundry (20 stars, last pushed 2d ago), licensed MIT. It adds 67 tokens to every session and 3,855 once invoked, about $0.0003 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-30.
Other skills, from other repositories
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…