Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git 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/rules/zscaler/zscaler-mcp-server/zms-graphql-conventions)<a href="https://agentmods.dev/rules/zscaler/zscaler-mcp-server/zms-graphql-conventions"><img src="https://agentmods.dev/badge/rules/zscaler/zscaler-mcp-server/zms-graphql-conventions.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.00227 | $0.00227 |
| Opus 5 | $0.00113 | $0.00113 |
| Sonnet 5 | $0.00045 | $0.00045 |
| Haiku 4.5 | $0.00023 | $0.00023 |
Grade A, and why
zms-graphql-conventions 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.
What it actually says
ZMS GraphQL conventions
- All ZMS operations use GraphQL queries via
POST /zms/graphql. There are no mutations — ZMS is read-only. - Every query requires
ZSCALER_CUSTOMER_ID, automatically resolved from the environment. - All Zscaler tools — ZMS included — authenticate exclusively through OneAPI against ZIdentity using the unified
ZSCALER_*credentials. - Two pagination patterns exist: some domains use
page/pageSize(agents, agent_groups, nonces), others usepageNum/pageSize(resources, resource_groups, policy_rules, app_zones, app_catalog, tags). eyez_idis the unique identifier for agents, agent groups, and nonces — not a numeric ID.- Tag hierarchy is three levels: namespace → key → value. Navigate top-down to list tag values.
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 · 14 lines · 227 tokens per session scan A 0c8bbb881581
zms-graphql-conventions is a cursor rule published in the GitHub repository zscaler/zscaler-mcp-server (50 stars, last pushed yesterday), licensed MIT. It adds 227 tokens to every session, about $0.0011 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 cursor rules, from other repositories
tools
MCP tool development patterns — factory pattern, base class, callbacks, and descriptions.
new-tool-from-docs
This rule generates tool implementations for the Razorpay MCP server based on API documentation.
php-client-implementation
Guidelines for implementing MCP clients in PHP.
php-server-implementation
Guidelines for implementing MCP servers in PHP.
301-framework-spring-boot
Spring Boot development guidelines.
mcp-development
Cursor rule "mcp-development" from floriscornel/todo-mcp, covering mcp development patterns, tool definition structure, error handling patterns, tool naming conventions and response formatting.