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/dongduong2001/pudo-code-system/devopsnpx skills add DongDuong2001/pudo-code-system --skill devopsgit clone --depth 1 https://github.com/DongDuong2001/pudo-code-systemWhat 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.00000 | $0.00439 |
| Opus 5 | $0.00000 | $0.00219 |
| Sonnet 5 | $0.00000 | $0.00088 |
| Haiku 4.5 | $0.00000 | $0.00044 |
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 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.
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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevOps Engineering Skill
Skill, Automation, Infrastructure, CI/CD
Context
Use this prompt when you need to configure CI/CD pipelines, write Infrastructure as Code (IaC), set up containerization, or manage deployments. This skill ensures the AI applies DevOps best practices such as least privilege, immutability, and declarative configuration.
Variables
{{infrastructure_tools}}: The tools you are using (e.g., GitHub Actions, Terraform, Docker, Kubernetes).{{environment}}: Target environment (e.g., Production AWS EKS, Staging Vercel).{{task_description}}: What needs to be automated or provisioned.
Prompt
Adopt the persona of a Senior DevOps Engineer. I need assistance with the following DevOps task:
Task: {{task_description}}
We are using the following infrastructure stack and tools:
{{infrastructure_tools}}
The target deployment environment is:
{{environment}}
Please provide a solution that adheres to the following DevOps principles:
1. **Infrastructure as Code (IaC):** Provide declarative configuration files, not manual step-by-step UI instructions.
2. **Security & Least Privilege:** Ensure IAM roles, service accounts, and network policies strictly follow the principle of least privilege. Do not hardcode secrets.
3. **Idempotency:** Ensure that running the automation or scripts multiple times results in the same state without causing errors.
4. **Observability:** If applicable, include health checks or logging configurations.
Walk me through the configuration, explaining any critical security or performance decisions.
Example Usage
Input:
Adopt the persona of a Senior DevOps Engineer. I need assistance with the following DevOps task:
Task: Create a CI pipeline that runs unit tests, builds a Docker image, and pushes it to AWS ECR.
We are using the following infrastructure stack and tools:
GitHub Actions, Docker, AWS ECR
The target deployment environment is:
AWS (us-east-1)
Please provide a solution that adheres to the following DevOps principles:
[...rest of prompt...]
What ships with it
11 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 · 48 lines · 0 tokens per session scan A 2b22fa37e939
devops is a skill published in the GitHub repository DongDuong2001/pudo-code-system (5 stars, last pushed 26d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 439 tokens. 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
docker-build-deploy
Use when containerizing a Node.js app and setting up GitHub Actions CI/CD to build, push to GHCR, and deploy via SSH. Multi-stage build, non-root user, caching.
cicd-pipeline-setup
Group skill: CI/CD pipeline setup — GitHub Actions, GitLab CI, Docker build, Kubernetes, Helm, Terraform, secrets, monitoring, and GitOps.
dev-environment-setup
Group skill: Set up a new development environment — project init, toolchain, package manager, dev container, editor config, git hooks, database, env vars, documentation, and CI/CD.
konflux-build
Create a manual Konflux build from a PR with configurable image expiry (default 30 days).
os-rust-backend-ci
Use this skill when the user wants to set up, configure, debug, or extend a GitHub Actions pipeline for a Rust backend that runs CI checks and produces a container image artifact in GHCR. Scope is testing + artifact only — deployment is intentionally out of scope. Trigger on: PR checks (fmt, clippy, tests, OpenAPI /…
aws-cloudformation-task-ecs-deploy-gh
Provides patterns to deploy ECS tasks and services with GitHub Actions CI/CD. Use when building Docker images, pushing to ECR, updating ECS task definitions, deploying ECS services, integrating with CloudFormation stacks, configuring AWS OIDC authentication for GitHub Actions, and implementing production-ready…