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/CLAUDE.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/claude-md)<a href="https://agentmods.dev/instructions/vinayaklatthe/microsoft-security-agent-toolkit/claude-md"><img src="https://agentmods.dev/badge/instructions/vinayaklatthe/microsoft-security-agent-toolkit/claude-md.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.00549 | $0.00549 |
| Opus 5 | $0.00275 | $0.00275 |
| Sonnet 5 | $0.00110 | $0.00110 |
| Haiku 4.5 | $0.00055 | $0.00055 |
Grade A, and why
microsoft-security-agent-toolkit CLAUDE.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 6d 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 — 35 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code instructions for microsoft-security-agent-toolkit
Always read HANDOFF.md at the repo root before making any change. It is the source of truth for design decisions, conventions, tool surface, and open work prioritization.
Quick context
- Repo role: action layer (MCP servers, KQL snippets, Logic Apps templates, demos) for AI agents working on Microsoft Security.
- Pairs with:
microsoft-security-skills(the knowledge layer, 88 skills, v0.2.0). - Status: preview — scaffold complete, MCP implementations pending.
Hard rules (do not violate)
- Never log or commit a tenant secret.
.envstays gitignored. - Every write tool (mutates tenant state) must take
confirm: trueand use the separate write-app registration. Seedocs/permissions-required.md. - Skills only declare
tools_required— they never bundle this toolkit. The host routes. - No offensive (red-team) tooling — defensive and governance only.
- No live-tenant calls in tests, demos, or samples — synthetic data only.
Conventions
- Conventional-commit-ish (
scaffold:,feat(sentinel-mcp):,docs:,kql:). Always addCo-authored-by: Copilot <[email protected]>when AI-assisted. - Branch off
main. PR intomain. One server / one snippet pack / one demo per PR. - KQL files use the header documented in
kql-snippets/README.md.
Tool IDs (do not rename without cross-repo update)
sentinel.run_kql, sentinel.list_incidents, sentinel.get_incident, sentinel.update_incident (write) ·
defender_xdr.list_alerts, defender_xdr.get_incident, defender_xdr.run_advanced_hunting, defender_xdr.update_incident (write), defender_xdr.isolate_device (write) ·
graph.signins, graph.risky_users, graph.directory_audit, graph.revoke_sessions (write), graph.disable_user (write) ·
purview_audit.search, purview_audit.export
When stuck
Pick the topmost unchecked item from "Open work" in HANDOFF.md. Phase 1 (sentinel-mcp end-to-end implementation) is the current priority.
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.
- 6d ago First seen · 35 lines · 549 tokens per session scan A 181a9bfe6285
microsoft-security-agent-toolkit CLAUDE.md is an instructions file published in the GitHub repository vinayaklatthe/microsoft-security-agent-toolkit (2 stars, last pushed 2mo ago), licensed MIT. It adds 549 tokens to every session, about $0.0027 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-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 caching.instructions.md
Caching patterns for .NET — IDistributedCache, Redis, in-memory, cache-aside, TTL strategies.
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.
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).
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).