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 reganomalley/claudia --skill claudia-devopsgit clone --depth 1 https://github.com/reganomalley/claudiaWrote 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/reganomalley/claudia/claudia-devops)<a href="https://agentmods.dev/skills/reganomalley/claudia/claudia-devops"><img src="https://agentmods.dev/badge/skills/reganomalley/claudia/claudia-devops/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/reganomalley/claudia/claudia-devops"><img src="https://agentmods.dev/badge/skills/reganomalley/claudia/claudia-devops.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.00104 | $0.01149 |
| Opus 5 | $0.00052 | $0.00575 |
| Sonnet 5 | $0.00021 | $0.00230 |
| Haiku 4.5 | $0.00010 | $0.00115 |
Grade A, and why
claudia-devops 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 8d 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claudia DevOps Domain
Overview
DevOps is about shipping with confidence and sleeping through the night. Automate the boring stuff, monitor the important stuff. If your deploy process has a wiki page with 15 manual steps, something has gone wrong.
Decision Trees
Deployment Strategy: Where Are You?
What are you deploying?
├── Static site (HTML, SPA, docs)
│ └── Netlify / Vercel / Cloudflare Pages -- just push to main
├── Simple app (one service, one database)
│ └── PaaS: Railway / Render / Fly.io -- git push deploys, managed infra
├── Multi-service (2-5 services talking to each other)
│ └── Container orchestration: Docker Compose → ECS / Cloud Run
├── Enterprise (many teams, compliance, multi-region)
│ └── Kubernetes + GitOps (ArgoCD / Flux)
└── Not sure
└── Start with PaaS. Move down only when you hit real limits.
CI/CD Pipeline Template
Every pipeline follows this shape:
lint → test → build → deploy staging → smoke test → deploy prod
Specifics:
├── Lint + type-check (fastest, catches dumb mistakes first)
├── Unit tests (fast, high coverage)
├── Build artifact (Docker image, static bundle, binary)
├── Deploy to staging (automatic on merge to main)
├── Smoke tests against staging (health check, critical paths)
├── Deploy to production (automatic or manual gate)
└── Post-deploy verification (synthetic monitoring, error rate check)
Deployment Patterns
| Pattern | How It Works | Use When | Risk |
|---|---|---|---|
| Rolling | Replace instances one at a time | Default for most apps | Brief mixed versions |
| Blue-Green | Run two identical envs, swap traffic | Zero-downtime required | 2x infrastructure cost |
| Canary | Route small % of traffic to new version | High-traffic, risk-averse | Complex routing setup |
| Feature Flags | Deploy code dark, enable for users | Decouple deploy from release | Flag debt accumulates |
| Recreate | Kill old, start new | Dev/staging, downtime OK | Downtime during deploy |
What ships with it
2 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.
- 8d ago First seen · 110 lines · 104 tokens per session scan A 25d042e1d325
claudia-devops is a skill published in the GitHub repository reganomalley/claudia (4 stars, last pushed 6mo ago), licensed MIT. It adds 104 tokens to every session and 1,149 once invoked, about $0.0005 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 skills, from other repositories
import-prom-rule
Bulk import of a Prometheus alert rule YAML file (create a whole set of rules at once). Dedicated to handling a remote URL or local YAML text, automatically parsing the three formats groups / a plain rules array / a single rule. ⚠️ Do not use this skill for single-rule creation — when the user describes a single alert…
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
configure-env-variables
Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides the user through linking site settings to those variables via the Power Pages Management app, adds the variables to the solution, and generates a…
atmos-profiles
Atmos profiles: profile directories, --profile and ATMOSPROFILE activation, profile merge behavior, environment switching, and routing profile-specific auth/toolchain/config overrides.
webhook-management
Configure and validate CCAM webhook targets across supported chat, incident, automation, and generic providers. Use when listing provider requirements, creating or updating a target, scoping it to alert rules, sending a test notification, reviewing delivery history, or deleting a target.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.