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/adonai-labs/agent-runwayWrote 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/rules/adonai-labs/agent-runway/devops-practices)<a href="https://agentmods.dev/rules/adonai-labs/agent-runway/devops-practices"><img src="https://agentmods.dev/badge/rules/adonai-labs/agent-runway/devops-practices/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/rules/adonai-labs/agent-runway/devops-practices"><img src="https://agentmods.dev/badge/rules/adonai-labs/agent-runway/devops-practices.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.01839 |
| Opus 5.5 | $0.00000 | $0.00736 |
| Sonnet 5.5 | $0.00000 | $0.00368 |
| Haiku 4.5 | $0.00000 | $0.00184 |
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 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.
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 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=highor 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-tofor 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
FROMfor each stage; do not mix build and runtime tools in the final image. - Use
--only=productionor 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:groupto avoid root-owned files. - Apply security updates in the base image (
apk update && apk upgradeor equivalent). - Remove cache, temp files, and unnecessary tools before final image.
Health checks and image size
- Add
HEALTHCHECKwithinterval,timeout,start-period, andretries. - Point health checks at a dedicated
/healthor similar endpoint; avoid heavy logic. - Prefer smaller base images (e.g.
-alpine); avoidlatesttag; pin versions. - Use
.dockerignoreto exclude build artefacts, tests, and docs from the build context.
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 · 200 lines · 0 tokens per session scan A 63da9e9baebb
devops-practices is a cursor rule published in the GitHub repository adonai-labs/agent-runway (2 stars, last pushed 17d 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.
Other cursor rules, from other repositories
optimize-dry-solid-principles-cursorrules-prompt-f
Cursor rules for optimization development with DRY and SOLID principles integration.
code-optimization
Guidelines for optimizing duplicate and poorly structured code.
language-agnostic-patterns
Language-agnostic programming patterns: SOLID, design patterns, clean code, and architecture. Load when refactoring, designing abstractions, or reviewing structure — not for everyday syntax.
code-review-en
Code Review Guidelines (English).
agent-master
Meta-orchestrator that classifies tasks and routes to the right combination of installed skills across caveman (output compression), superpowers (dev workflow), anthropic-skills (business/domain expertise), and wired tactical libraries (wshobson, davila7, impeccable, anthropic-official). 26 routing categories…
ai-dev-os-review
Performs a comprehensive self-review before creating a PR. Combines guideline compliance checking (L3) with design-level review (L2) and philosophical alignment (L1). Unlike @ai-dev-os-check which only checks rules, this also evaluates architecture decisions and code design quality.