Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add Kin9Zeus/senior-engineer-skills/plugin install senior-engineer-skillsWrote 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/kin9zeus/senior-engineer-skills/devops-platform)<a href="https://agentmods.dev/skills/kin9zeus/senior-engineer-skills/devops-platform"><img src="https://agentmods.dev/badge/skills/kin9zeus/senior-engineer-skills/devops-platform.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.00148 | $0.02203 |
| Opus 5 | $0.00074 | $0.01102 |
| Sonnet 5 | $0.00030 | $0.00441 |
| Haiku 4.5 | $0.00015 | $0.00220 |
Grade A, and why
devops-platform 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.
How it starts
The opening of the file, as written. The whole thing — 225 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevOps and Platform Engineering
Two questions decide whether a platform is professional:
How long from commit to production? How long from "this is broken" to it not being broken?
Everything below serves those two numbers. A pipeline that produces neither speed nor reversibility is ceremony.
Reproducibility — the precondition
If the environment cannot be rebuilt from the repository, everything else is built on sand.
- Runtime version pinned in a file the toolchain reads, and in the manifest.
- Lockfile committed; CI installs frozen (
npm ci,--frozen-lockfile,poetry install --sync,bundle --deployment). - Container base images pinned by digest, not by a moving tag.
- Infrastructure in code, in the repository, applied by the pipeline.
- No snowflake servers. Anything configured by hand once is a single point of failure with no recovery procedure. The test: could you delete the production environment and rebuild it from the repo?
- Local development one command away — Docker Compose, devcontainer, or a documented single script.
The pipeline
On every pull request, blocking merge:
install (frozen) → lint → typecheck → unit → integration → build → dependency audit → secret scan
On merge to the default branch:
build once, tag by commit SHA → deploy to staging → smoke tests → ready for production
Rules that matter more than the tool:
- Build the artefact once. Promote the same artefact through environments. Rebuilding per environment means you deployed something you never tested.
- CI must block merge. Establish this before there is pressure to bypass it; it is never established afterwards.
- Keep it under ~10 minutes. Beyond that, people stop waiting and start merging around it. Cache dependencies, parallelise, split slow suites.
- A flaky pipeline is a broken pipeline. A suite people re-run until green provides no information.
- Pin actions to a commit SHA, not a tag. Tags are mutable.
- Fork PRs must not access secrets.
- Branch protection: no direct pushes, review required, checks required.
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.
- 6d ago First seen · 225 lines · 148 tokens per session scan A 3ed892664aaa
devops-platform is a skill published in the GitHub repository Kin9Zeus/senior-engineer-skills (3 stars, last pushed 12d ago), licensed MIT. It adds 148 tokens to every session and 2,203 once invoked, about $0.0007 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
devops-engineer
Creates Dockerfiles, configures CI/CD pipelines, writes Kubernetes manifests, and generates Terraform/Pulumi infrastructure templates. Handles deployment automation, GitOps configuration, incident response runbooks, and internal developer platform tooling. Use when setting up CI/CD pipelines, containerizing…
deploy
Elixir/Phoenix deployment patterns — Dockerfile, fly.toml, runtime.exs, mix release, rel/ overlays. Use when configuring Fly.io, Docker, CI/CD, health checks, or production migrations.
devops-specialist
DevOps 与运维专家。精通 CI/CD、容器化、编排、基础设施即代码、监控告警和自动化部署。用于构建高效、可靠的软件交付流水线和运维系统。.
platform-skills
Use when troubleshooting, implementing, reviewing, or auditing platform infrastructure as a system — where Kubernetes, GitOps, CI/CD, and security concerns intersect. Provides structured diagnosis with blast radius, validation steps, and rollback plan for: Kubernetes, Flux CD, Argo CD, Terraform, GitHub Actions…
base-cn-registry-mirror-strategy
国内镜像源与代理分层策略（Docker / Debian / Alpine / Node / Python / Maven / Gradle / Go），用于 Dockerfile 与 CI 的可维护加速。.
devops
Deployment and infrastructure operations. Use when writing or debugging a Dockerfile, docker build/run, docker compose; running terraform plan/apply/destroy or editing .tf files and modules; using kubectl, debugging pods (CrashLoopBackOff, ImagePullBackOff, OOMKilled), applying manifests, or writing Helm charts…