Borrowing it
Nothing to install: this file belongs to vivekanjana76/azure-compliance-mcp. 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/vivekanjana76/azure-compliance-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/vivekanjana76/azure-compliance-mcpWrote 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/vivekanjana76/azure-compliance-mcp/claude-md)<a href="https://agentmods.dev/instructions/vivekanjana76/azure-compliance-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/vivekanjana76/azure-compliance-mcp/claude-md/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/vivekanjana76/azure-compliance-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/vivekanjana76/azure-compliance-mcp/claude-md.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.00668 | $0.00668 |
| Opus 5 | $0.00334 | $0.00334 |
| Sonnet 5 | $0.00134 | $0.00134 |
| Haiku 4.5 | $0.00067 | $0.00067 |
Grade A, and why
azure-compliance-mcp 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 10d 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — azure-compliance-mcp
What this is
An MCP server exposing Azure resource-compliance data (VM compliance, patch status, orphaned RBAC) so an LLM agent can query infrastructure health in natural language. Built with FastMCP 3.x.
Tech stack (pin these)
- Python 3.12+, managed with uv
- FastMCP 3.x (
from fastmcp import FastMCP) - azure-identity + azure-mgmt-resourcegraph (live mode only)
- pytest + ruff
- Transports: stdio (local), Streamable HTTP + OAuth 2.1 (remote)
Architecture
- server.py — FastMCP instance + 5–6 read-only tools
- providers/ — data layer, two modes:
- mock (default): synthetic, seeded, ARG-schema-shaped data incl. non-compliant resources
- live: real Azure Resource Graph against the user's OWN tenant via DefaultAzureCredential
- Mode via
--mode mock|live; default mock so the repo runs with zero Azure setup.
GitHub automation — how you (Claude) manage this repo
- Use the
ghCLI for ALL GitHub operations (it's authenticated; never ask for a token). - Repo metadata: description "MCP server for natural-language Azure compliance & infra-health queries"; topics: mcp, model-context-protocol, azure, devops, ai-agents, fastmcp, python.
- License: MIT.
- Workflow, every feature: open a GitHub issue -> branch
feat/NN-short-name-> implement -> commit ->gh pr createreferencing the issue -> wait for the user to merge. - NEVER push directly to main. main is protected.
- Conventional Commits: feat:, fix:, docs:, test:, chore:
- Before every push, run BOTH
uv run ruff check .ANDuv run ruff format --check .. - Tag releases (v0.1.0, ...) at milestones.
- Keep commits meaningful and scoped — no padding, no noise commits.
Hard rules — NEVER violate
- NEVER commit secrets, tenant IDs, connection strings, or .env (gitignored).
- NEVER use or commit real company/client data. Mock or personal-tenant data only.
- In stdio mode, NEVER write to stdout (no print()). Log to stderr only.
- All Azure tools are READ-ONLY. No tool may modify Azure resources.
- Keep the tool surface to 5–6 tools; update SPEC.md before adding any.
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.
- 10d ago First seen · 53 lines · 668 tokens per session scan A a0e36c912792
azure-compliance-mcp CLAUDE.md is an instructions file published in the GitHub repository vivekanjana76/azure-compliance-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 668 tokens to every session, about $0.0033 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
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).
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.
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).