operate-devops skillA
operate-devops is agent-read markdown (skill) from phelan164/codex-howto: Plan and implement infrastructure, CI/CD, container, deployment, observability, and operational configuration changes with least privilege, staged validation, and rollback awareness. Use for pipelines, infrastructure as code, Kubernetes, containers, release automation, monitoring, and production-readiness work; do not use to perform destructive production actions without explicit authorization..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Operate DevOps ## Workflow 1. Read repository and environment guidance before changing configuration. 2. Identify the target environment, current state, owning tool, blast radius, and approval boundary. 3. Separate diagnosis, proposed change, apply, verification, and rollback. 4. Prefer a dry run, plan, diff, render, lint, or local build before any apply step. 5. Make the smallest reversible change. 6. Validate configuration syntax and policy. 7. Test failure behavior and rollback in the safest available environment. 8. Review the diff for secrets, broad permissions, unpinned behavior, and unintended targets. ## Guardrails - Confirm account, cluster, subscription, region, namespace, and environment before state-changing commands. - Keep credentials out of code, command output, and generated artifacts. - Use least-privilege identities and scoped approvals. - Do not silently apply infrastructure because a plan succeeded. - Do not delete, force-replace, rotate, deploy, or migrate live resources without explicit authorization. - Preserve a recovery path for availability, routing, storage, and identity changes. - Do not weaken security controls merely to make automation pass. …
Read the whole file at its exact version.
How to install
mdr add phelan164/codex-howto/operate-devops@git:20260724.a8a7148mdr add phelan164/codex-howto/operate-devops@sha256:f8e8f76a8f7e8bc1Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_eoyduenlj6mafvzp)
1 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (2479 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
phelan164/codex-howto · 9 stars · license MIT · pushed 2026-09-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_eoyduenlj6mafvzp GET https://markdownregistry.com/api/v1/resolve?ref=phelan164/codex-howto/operate-devops GET https://markdownregistry.com/api/v1/blob/f8e8f76a8f7e8bc18a52dee91ad131e3f8407d008453a827dddb5c41fe281184
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.