Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/Kin9Zeus/senior-engineer-skillsnpx agentmods add skills/kin9zeus/senior-engineer-skills/devops-platformWrote 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/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/kin9zeus/senior-engineer-skills/devops-platform"><img src="https://agentmods.dev/badge/skills/kin9zeus/senior-engineer-skills/devops-platform.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.00148 | $0.02414 |
| Opus 5.5 | $0.00059 | $0.00966 |
| Sonnet 5.5 | $0.00030 | $0.00483 |
| Haiku 4.5 | $0.00015 | $0.00241 |
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 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 — 237 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.
- 2d ago Changed · +12 lines db371ac0bf60
- 1mo 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 2d ago), licensed MIT. It adds 148 tokens to every session and 2,414 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
iac-misconfig-scan
Scan infrastructure-as-code — Dockerfiles, Compose, Terraform, and GitHub Actions — for security misconfigurations like running as root, world-writable files, unpinned actions, and hardcoded secrets. Pure Claude Code, no signup.
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.
best-practices
Apply modern web development best practices for security, compatibility, and code quality. Use when asked to "apply best practices", "security audit", "modernize code", "code quality review", or "check for vulnerabilities".
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.
devops
Comprehensive DevOps engineering practices for Kubernetes, CI/CD, Bash scripting, Ansible, and cloud infrastructure.