devops-practices

A set of instructions for building and running software in production. It covers automated build-and-release pipelines, Docker containers, Kubernetes deployment, infrastructure configuration, monitoring, logs, and security.

In plain words
What is it for?
Use it when creating CI/CD workflows, Docker files, Kubernetes configurations, infrastructure code, deployment checks, monitoring, or logging.
Why use it?
It helps prevent untested code, insecure secrets, and deployments that fail without being checked.

Cursor rule

Install

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.

agentmods
npx agentmods add rules/adonai-labs/agent-runway/devops-practices
Clone the repo
git clone --depth 1 https://github.com/adonai-labs/agent-runway
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 1,839 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.01839
Opus 5 $0.00000 $0.00920
Sonnet 5 $0.00000 $0.00368
Haiku 4.5 $0.00000 $0.00184

Measured 2d ago against content hash 63da9e9baebb, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

devops-practices scanned grade A with 1 finding 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

HEALTHCHECK --interval=30s --timeout=3s --retries=3 CMD curl -f http://localhost:3000/health || exit 1
src/core/rules/devops-practices.mdc · 200 lines

How it starts

The opening of the file, as written. The whole thing — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.

DevOps Practices

Directives for CI/CD, containerisation, orchestration, IaC, monitoring, and logging.


CI/CD Pipeline Directives

Stages and quality gates

  • Use separate stages: test → build → deploy; do not run deploy without passing test and build.
  • Run lint, type-check, and unit tests before build; fail the pipeline on any failure.
  • Run security audit (npm audit --audit-level=high or equivalent) before build; treat high/critical as blocking.
  • Build and push images only after tests pass; tag images with commit SHA or short hash, not only latest.
  • Deploy only from protected branches (e.g. main); gate deployments on approval or environment checks.
  • Use matrix builds for multi-version testing when relevant; cache dependencies between jobs.
  • Upload coverage reports; fail if coverage falls below thresholds.

What to include

  • Checkout, dependency install, lint, test, security audit in sequence.
  • Build stage with caching (e.g. cache-from / cache-to for Docker).
  • Deploy stage with explicit rollout verification (e.g. kubectl rollout status).
  • Use secrets for credentials; never commit secrets or use env vars in config files.

Docker Directives

Multi-stage builds

  • Use multi-stage builds: separate build stage from runtime stage; copy only built artefacts.
  • Use FROM for each stage; do not mix build and runtime tools in the final image.
  • Use --only=production or equivalent for install when building runtime images.

Non-root and security

  • Create and use a non-root user; run as that user in the final stage.
  • Use COPY --chown=user:group to avoid root-owned files.
  • Apply security updates in the base image (apk update && apk upgrade or equivalent).
  • Remove cache, temp files, and unnecessary tools before final image.

Health checks and image size

  • Add HEALTHCHECK with interval, timeout, start-period, and retries.
  • Point health checks at a dedicated /health or similar endpoint; avoid heavy logic.
  • Prefer smaller base images (e.g. -alpine); avoid latest tag; pin versions.
  • Use .dockerignore to exclude build artefacts, tests, and docs from the build context.

Read the full file on GitHub · 200 lines

Changes

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.

  1. 2d ago First seen · 200 lines · 0 tokens per session scan A 63da9e9baebb

Subscribe to this mod's changes

devops-practices is a cursor rule published in the GitHub repository adonai-labs/agent-runway (2 stars, last pushed 12d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,839 tokens. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.