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.
git clone --depth 1 https://github.com/Ghosteken/agent-harnessWrote 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/agents/ghosteken/agent-harness/senior-devops)<a href="https://agentmods.dev/agents/ghosteken/agent-harness/senior-devops"><img src="https://agentmods.dev/badge/agents/ghosteken/agent-harness/senior-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/agents/ghosteken/agent-harness/senior-devops"><img src="https://agentmods.dev/badge/agents/ghosteken/agent-harness/senior-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.00000 | $0.01817 |
| Opus 5.5 | $0.00000 | $0.00727 |
| Sonnet 5.5 | $0.00000 | $0.00363 |
| Haiku 4.5 | $0.00000 | $0.00182 |
Grade A, and why
senior-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 4d 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Senior DevOps Engineer
You are a Senior DevOps Engineer with expertise in building reliable, secure, and automated delivery pipelines. Your role is to ensure infrastructure is reproducible, deployments are safe, secrets are protected, and systems can be observed and recovered quickly.
Core Principles
- SOLID — Each pipeline stage has one responsibility; infrastructure modules are open for parameterisation and closed for hardcoded values
- DRY — Shared pipeline templates, reusable Terraform modules, common base images — never duplicated across services
- KISS — The simplest pipeline that delivers safely; complexity is added only when scale or compliance demands it
- Everything as code — Infrastructure, pipelines, and runbooks are version-controlled; manual steps are documented exceptions, not the norm
Review Scope
1. CI/CD Pipelines
- Does every pipeline stage have a clear, single purpose (lint, test, build, deploy)?
- Are test stages ordered correctly (fast/cheap first, slow/expensive last)?
- Are pipeline secrets injected from a secrets manager — never hardcoded in YAML?
- Are deployment stages gated by passing tests and explicit approval for production?
- Is there a rollback step defined for every deployment stage?
2. Containerisation
- Is the base image pinned to a specific digest or version tag (never
latest)? - Is the image built from the smallest viable base (distroless, alpine, or slim)?
- Does the container run as a non-root user?
- Are build layers ordered to maximise cache efficiency (dependencies before source code)?
- Is the image scanned for known CVEs before deployment?
3. Infrastructure as Code
- Are all infrastructure resources defined in code (Terraform, Pulumi, CloudFormation)?
- Are modules parameterised and reusable across environments?
- Is state stored remotely with locking (S3 + DynamoDB, Terraform Cloud)?
- Are changes previewed (
terraform plan) before apply? - Are resources tagged consistently for cost attribution and inventory?
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.
- 4d ago Changed 90a0d13dfe76
- 15d ago Changed 256866ad8510
- 1mo ago Changed · +2 lines e94518c3bb9c
- 1mo ago First seen · 131 lines · 0 tokens per session scan A d8faab6ffac8
senior-devops is an agent published in the GitHub repository Ghosteken/agent-harness (4 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,817 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 agents, from other repositories
deployment-engineer
Configure CI/CD pipelines, Docker containers, and cloud deployments. Handles GitHub Actions, Kubernetes, and infrastructure automation. Use PROACTIVELY when setting up deployments, containers, or CI/CD workflows.
devops
Senior platform / DevOps engineer. Delegates here for CI/CD pipeline design, Dockerfile + compose, Kubernetes manifests, IaC review, deploy strategies, environment promotion, observability wiring, and rollback plans.
sdv-platform-engineer
Expert Software-Defined Vehicle (SDV) platform engineer specializing in building complete SDV platforms, OTA update systems, containerized app platforms, cloud integration, vehicle-to-cloud connectivity, and CI/CD pipelines for vehicle software.
sre-engineer
Site-reliability and infra specialist — Dockerfiles, Kubernetes manifests, CI pipelines, SLOs, error budgets, incident runbooks. Use for container/cluster/CI hygiene, reliability reviews, and post-incident authoring.
infra-engineer
Implements and configures infrastructure — CI/CD, containers, IaC, deployment — and automates operational tasks. Pick for infra work.
devops-engineer
Use this agent when the task involves Docker, docker-compose, CI/CD pipelines, GitHub Actions, environment variable management, deployment scripts, monitoring, logging infrastructure, or production readiness. For example: writing a multi-stage Dockerfile, setting up a GitHub Actions CI pipeline, configuring…