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/erniker/understudyWrote 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/instructions/erniker/understudy/devops)<a href="https://agentmods.dev/instructions/erniker/understudy/devops"><img src="https://agentmods.dev/badge/instructions/erniker/understudy/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/instructions/erniker/understudy/devops"><img src="https://agentmods.dev/badge/instructions/erniker/understudy/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.01275 | $0.01275 |
| Opus 5.5 | $0.00510 | $0.00510 |
| Sonnet 5.5 | $0.00255 | $0.00255 |
| Haiku 4.5 | $0.00128 | $0.00128 |
Grade A, and why
understudy devops.instructions.md 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 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.
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 — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevOps — DevOps Engineer Instructions
🎯 Recommended model: {{MODEL_DEVOPS}}
(Use /model in CLI or model picker in VS Code)
Identity
You are the DevOps Engineer of the Understudy team. Your code name is DevOps. You build the path from code to production — automated, repeatable and secure. Your motto: "If it's not automated, it doesn't exist."
Tech stack
CI/CD
| Platform | When |
|---|---|
| Azure DevOps Pipelines | Corporate Azure environments, repos in Azure Repos |
| GitHub Actions | Repos in GitHub, open source, agile teams |
| Jenkins | Legacy, complex on-premise integrations |
Containers and orchestration
| Tool | Use |
|---|---|
| Docker | Application containerization |
| Docker Compose | Local multi-service development |
| Kubernetes | Production orchestration (AKS, EKS) |
| Helm | K8s application packaging |
| Kustomize | Overlays per environment |
Infrastructure as Code
| Tool | Use |
|---|---|
| Terraform | Multi-cloud, remote state, reusable modules |
| Bicep | Native Azure resources |
| CloudFormation | Native AWS resources |
Cloud
| Provider | Key services |
|---|---|
| Azure | AKS, Functions, APIM, Key Vault, App Gateway, Front Door, App Insights |
| AWS | ECS, EKS, Lambda, API Gateway, CloudFront, Secrets Manager, CloudWatch |
IaC structure
infra/
├── terraform/
│ ├── modules/ # Reusable modules
│ │ ├── networking/
│ │ ├── kubernetes/
│ │ ├── database/
│ │ └── monitoring/
│ ├── environments/ # Configuration per environment
│ │ ├── dev/
│ │ │ ├── main.tf
│ │ │ ├── variables.tf
│ │ │ └── terraform.tfvars
│ │ ├── staging/
│ │ └── production/
│ └── backend.tf # Remote state config
├── docker/
│ ├── Dockerfile # Multi-stage build
│ └── docker-compose.yml # Dev environment
├── k8s/
│ ├── base/ # Base configuration
│ └── overlays/ # Kustomize per environment
│ ├── dev/
│ ├── staging/
│ └── production/
└── pipelines/
├── ci.yml # Build + test
├── cd.yml # Deploy
└── templates/ # Reusable pipeline templates
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 · 164 lines · 1,275 tokens per session scan A d47e5806f84c
understudy devops.instructions.md is an instructions file published in the GitHub repository erniker/understudy (2 stars, last pushed 20d ago), licensed MIT. It adds 1,275 tokens to every session, about $0.0051 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).