Borrowing it
Nothing to install: this file belongs to vinayaklatthe/microsoft-security-agent-toolkit. 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/vinayaklatthe/microsoft-security-agent-toolkit/main/.github/copilot-instructions.mdgit clone --depth 1 https://github.com/vinayaklatthe/microsoft-security-agent-toolkitWrote 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/vinayaklatthe/microsoft-security-agent-toolkit/copilot-instructions)<a href="https://agentmods.dev/instructions/vinayaklatthe/microsoft-security-agent-toolkit/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/vinayaklatthe/microsoft-security-agent-toolkit/copilot-instructions/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/vinayaklatthe/microsoft-security-agent-toolkit/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/vinayaklatthe/microsoft-security-agent-toolkit/copilot-instructions.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.00837 | $0.00837 |
| Opus 5.5 | $0.00335 | $0.00335 |
| Sonnet 5.5 | $0.00167 | $0.00167 |
| Haiku 4.5 | $0.00084 | $0.00084 |
Grade A, and why
microsoft-security-agent-toolkit 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 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copilot / AI agent instructions for microsoft-security-agent-toolkit
This file is automatically loaded as context by GitHub Copilot Chat in VS Code (and respected by most other VS Code AI agents) when working in this repo.
Read this first
Always read HANDOFF.md at the repo root before making any change. It contains the design decisions, conventions, and open work prioritization that you will not be able to infer from the code alone.
What this repo is
The action layer for AI agents working on Microsoft Security. Pairs with microsoft-security-skills (skills give the agent knowledge; this toolkit lets it act on live tenant data).
Status: preview. Scaffold complete; MCP server implementations pending.
Hard rules
- Never log or commit a tenant secret.
.envis gitignored. Do not add it back. Do not paste realCLIENT_SECRET/ tokens into commits, tests, or docs. - Every write tool (anything that mutates tenant state) must take an explicit
confirm: trueparameter, must be marked(write)in the server README's tool table, and must use the separate write-app registration documented indocs/permissions-required.md. - Skills do not bundle this toolkit. They only declare
tools_requiredin front-matter. The host routes the declaration to whichever provider is registered. Do not change this contract without updating both repos. - No offensive tooling. This is defensive-and-governance only. Generic red-team content belongs elsewhere.
- No live tenant calls in tests, demos, or samples. Use synthetic data.
Conventions
- Conventional-commit-ish messages (
scaffold:,feat(sentinel-mcp):,docs:,kql:). Always includeCo-authored-by: Copilot <[email protected]>when AI-assisted. - Branch off
main, open a PR — do not merge directly. - One server / one snippet pack / one demo per PR.
- KQL files in
kql-snippets/must have the header documented inkql-snippets/README.md(Title / MITRE / Data source / Use case / Tuning / Author / License). - MCP server READMEs must follow the contract documented in
HANDOFF.md(Tool ID table → Configuration → Alternatives → Cross-links).
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 · 51 lines · 837 tokens per session scan A 2c9e5359f2bc
microsoft-security-agent-toolkit copilot-instructions.md is an instructions file published in the GitHub repository vinayaklatthe/microsoft-security-agent-toolkit (2 stars, last pushed 4mo ago), licensed MIT. It adds 837 tokens to every session, about $0.0033 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
plan-forge dapr.instructions.md
Dapr patterns for .NET — building blocks, component config, sidecar architecture, multi-tenant isolation, workflows, state management, secrets.
plan-forge database.instructions.md
Database patterns for .NET — Dapper/EF Core 10, parameterized queries, migration strategy.
plan-forge caching.instructions.md
Caching patterns for .NET — IDistributedCache, Redis, in-memory, cache-aside, TTL strategies.
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).