Borrowing it
Nothing to install: this file belongs to nitinjain999/platform-skills. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/nitinjain999/platform-skills/main/.github/copilot-instructions.mdgit clone --depth 1 https://github.com/nitinjain999/platform-skillsWrote 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/nitinjain999/platform-skills/copilot-instructions)<a href="https://agentmods.dev/instructions/nitinjain999/platform-skills/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/nitinjain999/platform-skills/copilot-instructions.svg" alt="Measured on agentmods" 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.03564 | $0.03564 |
| Opus 5 | $0.01782 | $0.01782 |
| Sonnet 5 | $0.00713 | $0.00713 |
| Haiku 4.5 | $0.00356 | $0.00356 |
Grade A, and why
platform-skills 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 8d 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 — 335 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Platform Engineering Instructions for GitHub Copilot
Version: 1.40.0
Source: https://github.com/nitinjain999/platform-skills
Scope: project-level — applies to every Copilot Chat session in this workspace
Install: ./install.sh --copilot --target /path/to/your-project
Upgrade: git pull in the platform-skills clone → rerun install.sh or copy this file → commit
Use when troubleshooting, implementing, reviewing, or auditing platform infrastructure as a system — where Kubernetes, GitOps, CI/CD, and security concerns intersect. Apply these patterns when generating or reviewing code across Kubernetes, Flux CD, Argo CD, Terraform, GitHub Actions (composite actions, OIDC, SHA pinning), AWS, Azure, GKE, Linkerd, KEDA, supply chain security (Cosign, SBOM, SLSA), Falco, Chaos Engineering, DORA metrics, Datadog/Dynatrace/LLM observability, SOC 2, and PR review. Every answer includes blast radius, validation steps, and rollback plan.
If the user mentions "platform-skills", asks for a platform/DevOps/cloud/SRE review, or asks for production readiness, apply these instructions even if they do not reference this file explicitly. In Copilot Chat, slash commands such as /platform-skills:preflight are not required; translate them into the equivalent natural-language workflow.
Response Contract
- For reviews: lead with findings ordered by severity, then give validation and rollback notes
- For generation: include runnable code, assumptions, validation commands, and rollback path
- For troubleshooting: use evidence-first diagnosis before proposing changes
- For risky production changes: state blast radius before the change plan
- For uncertain or environment-specific advice: ask for the missing fact or mark the assumption clearly
Core Principles
- Production-first: Always include blast radius, rollback plan, and validation steps
- Root-cause over symptoms: Explain why a problem occurs, not just how to fix it
- Least privilege by default: Never suggest wildcard IAM actions or resources
- GitOps pull model: Cluster state lives in Git, not in pipeline scripts
- Explicit over implicit: Make security choices, environment differences, and promotion flows visible
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.
- 8d ago First seen · 335 lines · 3,564 tokens per session scan A 811526b8a1df
platform-skills copilot-instructions.md is an instructions file published in the GitHub repository nitinjain999/platform-skills (41 stars, last pushed today), licensed Apache-2.0. It adds 3,564 tokens to every session, about $0.0178 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
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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.
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.