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.
npx agentmods add instructions/versuscontrol/devops-ai-guidelines/copilot-instructionsgit clone --depth 1 https://github.com/VersusControl/devops-ai-guidelinesWhat 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 | $0.00410 | $0.00410 |
| Opus 5 | $0.00205 | $0.00205 |
| Sonnet 5 | $0.00082 | $0.00082 |
| Haiku 4.5 | $0.00041 | $0.00041 |
Grade A, and why
devops-ai-guidelines copilot-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 3d 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.
What it actually says
Copilot instructions: Kubernetes MCP workspace
You are assisting an SRE/DevOps engineer who manages Kubernetes clusters
through a local MCP server (k8s-mcp-server). The server exposes the
following capabilities:
- Resources:
pods,services,deployments,configmaps,secrets,namespaces. - Tools:
list_pods,get_pod_logs,restart_pod,scale_deployment,describe_resource,delete_pod,create_configmap.
Operating rules
- Prefer MCP tools over
kubectl. When the user asks about cluster state, calllist_pods,describe_resource, etc. Do not synthesise answers from memory. - Always include
namespacearguments. Default todefaultonly when the user did not specify one and confirm in the response. - Destructive operations require explicit confirmation. For
restart_pod,delete_pod, orscale_deploymentwithreplicas=0, restate the action and require the user to replyyesbefore invoking the tool. Setconfirm: trueonly after explicit consent. - Format output for fast scanning. Use compact tables for lists and fenced YAML blocks for resource manifests.
- Cite tool results. When summarising, reference the tool name and
relevant fields (e.g. "via
list_pods→ 3/3 Ready").
Code style for Go contributions
- Target Go 1.23+, use standard
log/slog-style structured logging. - Use
context.Contextas the first argument on any function that does I/O. - Wrap external errors with
fmt.Errorf("...: %w", err). - Keep MCP tool handlers thin: validate → delegate to
pkg/k8s→ format.
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.
- 3d ago First seen · 34 lines · 410 tokens per session scan A c419ac195d72
devops-ai-guidelines copilot-instructions.md is an instructions file published in the GitHub repository VersusControl/devops-ai-guidelines (1,451 stars, last pushed 12d ago), licensed MIT. It adds 410 tokens to every session, about $0.0020 per session on Opus 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-30.
Other instructions, from other repositories
manifold AGENTS.md
Instructions for intelligencedev/manifold, covering go/manifold, coding conventions, project structure & module organization, package organization and dependency injection.
loadout go.instructions.md
Go Engineering Instructions (CLI + API, framework-agnostic).
finfocus go-files.instructions.md
Instructions for rshade/finfocus, covering go code instructions, go version requirements, code quality standards, security best practices and performance considerations.
finfocus go-test-files.instructions.md
Instructions for rshade/finfocus, covering go test files instructions, test structure, test coverage requirements, testing patterns and test organization.
finfocus go-module.instructions.md
Instructions for rshade/finfocus, covering go module instructions, go version management, dependency management, module organization and security considerations.
no-mistakes AGENTS.md
AGENTS.md instructions for kunchenguid/no-mistakes, covering agents.md and maintaining this file.