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/commands/zscaler/zscaler-mcp-server/compare-locations)<a href="https://agentmods.dev/commands/zscaler/zscaler-mcp-server/compare-locations"><img src="https://agentmods.dev/badge/commands/zscaler/zscaler-mcp-server/compare-locations/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/commands/zscaler/zscaler-mcp-server/compare-locations"><img src="https://agentmods.dev/badge/commands/zscaler/zscaler-mcp-server/compare-locations.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.00020 | $0.00683 |
| Opus 5 | $0.00010 | $0.00342 |
| Sonnet 5 | $0.00004 | $0.00137 |
| Haiku 4.5 | $0.00002 | $0.00068 |
Grade A, and why
compare-locations 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.
How it starts
The opening of the file, as written. The whole thing — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Compare Location Experience
Compare locations: $ARGUMENTS
Step 1: Parse Input
Extract:
- Application (optional -- compare across all apps)
- Locations to compare (optional -- compare all)
- Time window in hours (default: 24)
Step 2: Get Application Scores by Location
zdx_list_applications()
```text
For each application:
```text
zdx_get_application(app_id="<app_id>", since=<hours>)
```text
## Step 3: Break Down by Location/Department
```text
zdx_list_devices(app_id="<app_id>")
```text
Group devices by location and calculate average scores per location.
## Step 4: Investigate Outliers
For locations with significantly worse scores:
```text
zdx_get_application_metric(app_id="<app_id>", metric_name="dns_time", since=<hours>)
```text
Check key metrics to identify the bottleneck.
## Step 5: Check Location-Specific Alerts
```text
zdx_list_alerts(since=<hours>)
```text
Correlate alerts with location data.
## Step 6: Present Report
**ALWAYS present data in HTML tables** using `<table>`, `<thead>`, `<tbody>`, `<tr>`, `<th>`, `<td>` tags with inline styling. Use color-coded rows: green (score 66-100), yellow (score 34-65), red (score 0-33).
Include:
1. **Location ranking table** (rank, location, score, PFT, DNS, availability, poor users, active alerts)
2. **Detailed analysis** explaining the performance differences between locations and what patterns they reveal
3. **Root cause** for the worst performer(s) -- what specific metric is the bottleneck and why it's location-specific
4. **Next steps / resolution** per location:
- Critical locations: investigate DNS/ISP infrastructure, compare config with healthy sites
- Borderline locations: monitor closely, review ISP paths
- Healthy locations: no action, use as reference baseline for comparison
## Step 7: Generate Downloadable Artifacts — MANDATORY
**You MUST create BOTH files. Do NOT skip the HTML page.**
1. **Word document** (`location_comparison_report_<date>.docx`): Executive summary, location ranking table, per-location analysis for underperformers, root cause per site, cross-location metric comparison, site-specific remediation actions.
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 · 81 lines · 20 tokens per session scan A 8acf037ef5b7
compare-locations is a command published in the GitHub repository zscaler/zscaler-mcp-server (50 stars, last pushed 2d ago), licensed MIT. It adds 20 tokens to every session and 683 once invoked, about $0.0001 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 commands, from other repositories
review-epo-claims
Analyze patent claims for EPO Art. 84 EPC compliance - clarity, conciseness, support by description.
ingest-dev
Ingest a URL, directory, or file into your knowledge base. remember = a specific durable fact, ingest = a URL, learn = a distilled lesson that gets retrieval preference.
resume
Auto-detect and resume any interrupted Plan Cascade task. Detects mega-plan, hybrid-worktree, or hybrid-auto context and routes to the appropriate resume command.
primer
Start with reading the CLAUDE.md file if it exists to get an understanding of the project.
infinite
INFINITE AGENTIC LOOP COMMAND.
next
You just finished a slash command or a batch of work. The user monitors via Farmer on their phone and cannot see CLI text output.