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/cross-service-overlap)<a href="https://agentmods.dev/rules/zscaler/zscaler-mcp-server/cross-service-overlap"><img src="https://agentmods.dev/badge/rules/zscaler/zscaler-mcp-server/cross-service-overlap/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/rules/zscaler/zscaler-mcp-server/cross-service-overlap"><img src="https://agentmods.dev/badge/rules/zscaler/zscaler-mcp-server/cross-service-overlap.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.00166 | $0.00166 |
| Opus 5 | $0.00083 | $0.00083 |
| Sonnet 5 | $0.00033 | $0.00033 |
| Haiku 4.5 | $0.00017 | $0.00017 |
Grade A, and why
cross-service-overlap 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 9d 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
Cross-service data overlap
Zscaler APIs expose overlapping data across services. For example, ZIA has device management tools (zia_list_devices) that return the same data as ZCC tools. Disabling the zcc service removes all zcc_* tools but does NOT remove ZIA's device tools. Use --disabled-tools with patterns to block cross-service data access when needed.
When a service is disabled, the zscaler_get_available_services tool lists it as disabled. Tool search returns the "closest N" results even if none are relevant — always check available services first to avoid using unrelated tools from other services.
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.
- 9d ago First seen · 11 lines · 166 tokens per session scan A 72500b53449a
cross-service-overlap is a cursor rule published in the GitHub repository zscaler/zscaler-mcp-server (50 stars, last pushed yesterday), licensed MIT. It adds 166 tokens to every session, about $0.0008 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
about-codebase
General information about the Lineai MCP Server codebase and its purpose.
runwhen-infrastructure
Infrastructure conventions for scripts targeting Kubernetes and databases via RunWhen runners.
validate-design-early
Ask for design approval before implementing 100+ lines.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.