Borrowing it
Nothing to install: this file belongs to zscaler/zscaler-mcp-server. 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/zscaler/zscaler-mcp-server/master/CLAUDE.mdgit clone --depth 1 https://github.com/zscaler/zscaler-mcp-serverWrote 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/zscaler/zscaler-mcp-server/claude-md)<a href="https://agentmods.dev/instructions/zscaler/zscaler-mcp-server/claude-md"><img src="https://agentmods.dev/badge/instructions/zscaler/zscaler-mcp-server/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.37325 | $0.37325 |
| Opus 5 | $0.18662 | $0.18662 |
| Sonnet 5 | $0.07465 | $0.07465 |
| Haiku 4.5 | $0.03732 | $0.03732 |
Grade A, and why
zscaler-mcp-server 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 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 — 1,252 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Zscaler MCP Server
254 read tools (plus write tools, off by default) for managing the Zscaler Zero Trust Exchange. Services: ZPA, ZIA, ZDX, ZCC, ZCell, EASM, Z-Insights, ZIdentity, ZTW (Zscaler Workload Segmentation), ZMS (Zscaler Microsegmentation).
Cross-tool conventions. The most-violated rules in this repo are mirrored at
.claude/CONVENTIONS.md(Claude Code) so they survive even if this file is trimmed. A parallel Cursor mirror at.cursor/rules/zscaler-conventions.mdc(auto-applied in Cursor sessions) is planned but not yet committed — until it lands, Cursor sessions rely on thisCLAUDE.mdbeing loaded explicitly. The full convention set lives below; Helper-file convention is in Helper File Convention (DO NOT FRAGMENT) — read it before adding any new file underzscaler_mcp/common/.
Architecture Overview
Core Components
zscaler_mcp/
├── server.py # ZscalerMCPServer class, CLI entrypoint, security posture logging
├── services.py # Service registry + 9 concrete service classes (ZPA, ZIA, ZDX, ZCC, ZTW, ZIdentity, ZEASM, ZInsights, ZMS)
├── auth.py # Auth middleware factory (JWT, API-key, Zscaler, OAuthProxy stub)
├── client.py # Zscaler SDK client factory (OneAPI only — single ZIdentity-based credential flow)
├── security.py # HTTP security warnings (TLS, plaintext)
├── cloud/
│ └── gcp_secrets.py # GCP Secret Manager credential loader (opt-in via ZSCALER_MCP_GCP_SECRET_MANAGER=true)
├── common/
│ ├── tool_helpers.py # register_read_tools / register_write_tools with disabled_tools filtering
│ ├── jmespath_utils.py # apply_jmespath() — caller-opt-in `query` filtering, wired centrally in registry/fastmcp_bridge.py
│ ├── elicitation.py # SEP-2322 native confirmation + HMAC token fallback for destructive actions
│ └── logging.py # log_security_warning helper
└── tools/ # 142 tool modules organized by service (zia/, zpa/, zdx/, zcc/, zcell/, ztw/, zid/, easm/, zins/, zms/)
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 · 1,252 lines · 37,325 tokens per session scan A 0ea7cfcd43a5
zscaler-mcp-server CLAUDE.md is an instructions file published in the GitHub repository zscaler/zscaler-mcp-server (50 stars, last pushed yesterday), licensed MIT. It adds 37,325 tokens to every session, about $0.1866 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
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).
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.
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.