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/tamnguyendinh/anvien/devopsnpx skills add tamnguyendinh/Anvien --skill devopsgit clone --depth 1 https://github.com/tamnguyendinh/AnvienWrote 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/tamnguyendinh/anvien/devops)<a href="https://agentmods.dev/skills/tamnguyendinh/anvien/devops"><img src="https://agentmods.dev/badge/skills/tamnguyendinh/anvien/devops.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.1 | $0.00014 | $0.00798 |
| Opus 5 | $0.00007 | $0.00399 |
| Sonnet 5 | $0.00003 | $0.00160 |
| Haiku 4.5 | $0.00001 | $0.00080 |
Grade A, and why
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 6d 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.
This is a copy
86% identical to ck:devops — 5 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevOps Skill
Deploy and manage cloud infrastructure across Cloudflare, Docker, Google Cloud, and Kubernetes.
When to Use
- Deploy serverless apps to Cloudflare Workers/Pages
- Containerize apps with Docker, Docker Compose
- Manage GCP with gcloud CLI (Cloud Run, GKE, Cloud SQL)
- Kubernetes cluster management (kubectl, Helm)
- GitOps workflows (Argo CD, Flux)
- CI/CD pipelines, multi-region deployments
- Security audits, RBAC, network policies
Platform Selection
| Need | Choose |
|---|---|
| Sub-50ms latency globally | Cloudflare Workers |
| Large file storage (zero egress) | Cloudflare R2 |
| SQL database (global reads) | Cloudflare D1 |
| Containerized workloads | Docker + Cloud Run/GKE |
| Enterprise Kubernetes | GKE |
| Managed relational DB | Cloud SQL |
| Static site + API | Cloudflare Pages |
| Container orchestration | Kubernetes |
| Package management for K8s | Helm |
Quick Start
# Cloudflare Worker
wrangler init my-worker && cd my-worker && wrangler deploy
# Docker
docker build -t myapp . && docker run -p 3000:3000 myapp
# GCP Cloud Run
gcloud run deploy my-service --image gcr.io/project/image --region us-central1
# Kubernetes
kubectl apply -f manifests/ && kubectl get pods
Reference Navigation
Cloudflare Platform
cloudflare-platform.md- Edge computing overviewcloudflare-workers-basics.md- Handler types, patternscloudflare-workers-advanced.md- Performance, optimizationcloudflare-workers-apis.md- Runtime APIs, bindingscloudflare-r2-storage.md- Object storage, S3 compatibilitycloudflare-d1-kv.md- D1 SQLite, KV storebrowser-rendering.md- Puppeteer automation
Docker
docker-basics.md- Dockerfile, images, containersdocker-compose.md- Multi-container apps
Google Cloud
gcloud-platform.md- gcloud CLI, authenticationgcloud-services.md- Compute Engine, GKE, Cloud Run
Kubernetes
kubernetes-basics.md- Core concepts, architecture, workloadskubernetes-kubectl.md- Essential commands, debugging workflowkubernetes-helm.md/kubernetes-helm-advanced.md- Helm charts, templateskubernetes-security.md/kubernetes-security-advanced.md- RBAC, secretskubernetes-workflows.md/kubernetes-workflows-advanced.md- GitOps, CI/CDkubernetes-troubleshooting.md/kubernetes-troubleshooting-advanced.md- Debug
What ships with it
28 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.
- .env.example 2.5 KB
- references/browser-rendering.md 6.8 KB
- references/cloudflare-d1-kv.md 2.5 KB
- references/cloudflare-platform.md 7.1 KB
- references/cloudflare-r2-storage.md 6.1 KB
- references/cloudflare-workers-advanced.md 7.1 KB
- references/cloudflare-workers-apis.md 6.8 KB
- references/cloudflare-workers-basics.md 8.6 KB
- references/docker-basics.md 5.7 KB
- references/docker-compose.md 4.7 KB
- references/gcloud-platform.md 6.9 KB
- references/gcloud-services.md 5.8 KB
- references/kubernetes-basics.md 1.7 KB
- references/kubernetes-helm-advanced.md 1.7 KB
- references/kubernetes-helm.md 1.8 KB
- references/kubernetes-kubectl.md 1.7 KB
- references/kubernetes-security-advanced.md 1.8 KB
- references/kubernetes-security.md 1.7 KB
- references/kubernetes-troubleshooting-advanced.md 1.4 KB
- references/kubernetes-troubleshooting.md 1.4 KB
- references/kubernetes-workflows-advanced.md 1.3 KB
- references/kubernetes-workflows.md 1.6 KB
- scripts/cloudflare_deploy.py 7.5 KB runs code
- scripts/docker_optimize.py 11 KB runs code
- scripts/requirements.txt 471 B
- scripts/tests/requirements.txt 52 B
- scripts/tests/test_cloudflare_deploy.py 9.0 KB runs code
- scripts/tests/test_docker_optimize.py 13 KB runs code
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.
- 6d ago First seen · 97 lines · 14 tokens per session scan A 7e1a148e9590
devops is a skill published in the GitHub repository tamnguyendinh/Anvien (9 stars, last pushed 2d ago), licensed MIT. It adds 14 tokens to every session and 798 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to ck:devops, differing in 5 lines, and is treated as a copy.
Other skills, from other repositories
multi-service-orchestration
PM2 process management, backend/frontend cascade execution, parallel worktree builds, and cross-service integration testing.
swarm-orchestrate
Optional autonomy control plane — configure, plan, launch, monitor, recover, or stop local CLI-agent workers through SwarmVault's durable supervisor. Use for fit/budget-aware platform + model + reasoning-effort routing; a consistent pre-start/live/boundary/on-demand board with ticket drill-down; TOLD/MEASURED/EST…
swarm-design-deep
The developer-driven design lane — the user commits to each approach before anything is written, then the design goes to pseudocode, algorithms, invariants, sequence diagrams and test vectors in their chosen design language. Use when the user wants to own the system rather than receive it: "developer mode"…
swarm-flow
The SDLC router — figures out where a project stands and runs the right phase. Use at the START of any work in a SwarmVault project: continuing/resuming a project, starting a new one, "what's next", or before writing any feature code, spec, design, or ticket. Also use when unsure which phase (requirements, design…
swarm-design-ui
UI/UX design phase — propose an intentional design system (pattern, brand, color, typography, spacing, atomic components) with the user, offering distinct directions and per-page layout options, for any interface type: Web, Mobile, Desktop, TUI, or CLI. Use when the SRS declares a user interface, when defining a…
swarm-vault
The vault contract — how any agent reads, writes, and queries the SwarmVault. Use at the start of work in any vault-connected project, before exploring the repo, when deciding where to record memory/plans/decisions/sessions, when handing off between sessions or agents, or whenever unsure how the vault works.