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 DauQuangThanh/hanoi-rainbow --skill devopsgit clone --depth 1 https://github.com/DauQuangThanh/hanoi-rainbowWrote 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/dauquangthanh/hanoi-rainbow/devops)<a href="https://agentmods.dev/skills/dauquangthanh/hanoi-rainbow/devops"><img src="https://agentmods.dev/badge/skills/dauquangthanh/hanoi-rainbow/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/dauquangthanh/hanoi-rainbow/devops"><img src="https://agentmods.dev/badge/skills/dauquangthanh/hanoi-rainbow/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.00141 | $0.01044 |
| Opus 5.5 | $0.00056 | $0.00418 |
| Sonnet 5.5 | $0.00028 | $0.00209 |
| Haiku 4.5 | $0.00014 | $0.00104 |
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 1mo 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevOps
Core Capabilities
Provides expert guidance covering the entire software delivery lifecycle:
- CI/CD Pipeline Design - Automated build, test, and deployment workflows
- Infrastructure as Code - Cloud resource provisioning with Terraform, CloudFormation, Bicep
- Container Orchestration - Docker and Kubernetes deployment patterns
- Deployment Strategies - Blue-green, canary, and rolling deployments
- Monitoring & Observability - Metrics, logging, alerting with Prometheus, Grafana, ELK
- Configuration Management - Ansible, Chef, Puppet automation
- Security & Compliance - DevSecOps practices and container security
Best Practices
CI/CD
- Keep pipelines fast (< 10 minutes for feedback)
- Fail fast with quick tests first
- Use pipeline as code (version controlled)
- Implement proper secret management
- Enable artifact caching and parallelize independent jobs
Infrastructure as Code
- Use remote state with locking
- Create reusable modules and pin versions
- Always review plan before apply
- Implement proper tagging strategy
- Document resource dependencies
Container Orchestration
- Set resource requests and limits
- Implement health checks (liveness/readiness probes)
- Use pod anti-affinity for high availability
- Enable horizontal pod autoscaling
- Implement proper logging and monitoring
Deployment
- Use rolling updates with zero downtime
- Implement proper health checks and rollback capabilities
- Use canary/blue-green for critical applications
- Test thoroughly in staging environments
- Monitor post-deployment metrics
Security
- Run containers as non-root with read-only root filesystems
- Scan images for vulnerabilities regularly
- Implement network policies and secrets management
- Enable pod security standards and least privilege access
Monitoring
- Collect metrics using RED/USE methods
- Implement structured logging with meaningful alerts
- Create actionable dashboards and monitor SLIs/SLOs
- Set up distributed tracing for microservices
What ships with it
9 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.
- references/cicd-pipeline-design.md 4.6 KB
- references/common-commands.md 2.3 KB
- references/configuration-management.md 1.9 KB
- references/container-orchestration.md 4.3 KB
- references/deployment-strategies.md 2.9 KB
- references/infrastructure-as-code.md 3.8 KB
- references/monitoring-and-observability.md 4.0 KB
- references/security-best-practices.md 2.3 KB
- references/troubleshooting-guide.md 1.2 KB
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.
- 1mo ago First seen · 116 lines · 141 tokens per session scan A b7878b7f2b02
devops is a skill published in the GitHub repository DauQuangThanh/hanoi-rainbow (17 stars, last pushed 9mo ago), licensed MIT. It adds 141 tokens to every session and 1,044 once invoked, about $0.0006 per session on Opus 5.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
github-actions-templates
Create production-ready GitHub Actions workflows for automated testing, building, and deploying applications. Use when setting up CI/CD with GitHub Actions, automating development workflows, or creating reusable workflow templates.
moai-ref-secops
DevSecOps, container, and API operational defensive security reference: CI/CD pipeline hardening, secret scanning, IaC misconfiguration detection, SAST/DAST integration, container image scanning, Kubernetes RBAC hardening, container-escape defense, runtime threat detection, OWASP API Top 10 operational defense, WAF…
nw-infrastructure-and-observability
Infrastructure as Code patterns (Terraform, Kubernetes), observability design (SLOs, metrics, alerting, dashboards), and pipeline security stages. Load when designing infrastructure, observability, or security scanning.
deployment
Use when taking an app from source to live: choosing the deploy target from requirements (Hetzner+Coolify vs Vercel vs a third), then wiring container → CI → registry → host with build secrets, healthchecks and rollback. NOT one platform's mechanics (that is coolify, vercel, railway, render), NOT the Dockerfile alone…
qa-security-testing
Builds security testing pipelines for SAST, DAST, SCA, secrets, containers. Use when wiring scanners into CI or regression gates.
windows-image-updater
Automates Windows container image migration for OneBranch pipelines. Bumps AdoPipelineGeneration package, regenerates pipeline configs via ConfigGen, and verifies old image reference is removed. Use for LTSC2019 to LTSC2022 migration, container image updates, OneBranch pipeline image upgrades.