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/troubleshoot-connector)<a href="https://agentmods.dev/commands/zscaler/zscaler-mcp-server/troubleshoot-connector"><img src="https://agentmods.dev/badge/commands/zscaler/zscaler-mcp-server/troubleshoot-connector/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/troubleshoot-connector"><img src="https://agentmods.dev/badge/commands/zscaler/zscaler-mcp-server/troubleshoot-connector.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.00025 | $0.00740 |
| Opus 5 | $0.00013 | $0.00370 |
| Sonnet 5 | $0.00005 | $0.00148 |
| Haiku 4.5 | $0.00003 | $0.00074 |
Grade B, and why
troubleshoot-connector scanned grade B with 2 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 12d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- Check disk: `sudo df -h` (min 100MB free required) Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Check memory: `curl -s 127.0.0.1:9000/memory/status` How it starts
The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Troubleshoot App Connector
Troubleshoot connector: $ARGUMENTS
Step 1: Parse Input
Extract:
- Connector or connector group name
- Symptom: not enrolling, disconnected, upgrade failed, high CPU/memory/disk, applications unreachable
Step 2: Inspect Connector Status
List and inspect individual connectors directly:
zpa_list_app_connectors(search="<name>")
zpa_get_app_connector(connector_id="<id>")
```text
Check `runtime_status`:
- `ZPN_STATUS_AUTHENTICATED` = healthy
- `ZPN_STATUS_DISCONNECTED` = lost connection
- `ZPN_STATUS_NOT_ENROLLED` = enrollment failed
Also check `current_version`, `expected_version`, `last_broker_connect_time`, `private_ip`, `public_ip`.
Then inspect the connector group for group-level settings:
```text
zpa_list_app_connector_groups(search="<group_name>")
zpa_get_app_connector_group(group_id="<id>")
```text
## Step 3: Check Provisioning Keys
```text
zpa_list_provisioning_keys(key_type="connector")
```text
Verify:
- Key `max_usage` vs current count (exhausted = no new enrollments)
- Key is enabled and not expired
- Key `component_id` matches the target connector group
## Step 4: Verify Infrastructure Chain
```text
zpa_list_server_groups()
zpa_list_application_segments()
```text
Confirm server groups reference this connector group and application segments use those server groups.
## Step 5: Diagnose by Symptom
**Not Enrolling:**
- Provisioning key exhausted → increase `max_usage` or create new key
- DNS failure → connector must resolve `co2br.<cloud>.net`
- SSL interception on path → allowlist ZPA domains
- Clock skew → sync NTP
- VM migration → wipe and re-provision
**Disconnected:**
- Network/firewall blocking TCP 443 to ZPA Public Service Edges
- SSL interception breaking TLS to brokers
- Check firewall requirements at `config.zscaler.com/<cloud>/zpa`
**Upgrade Failed:**
- Cannot reach `dist.private.zscaler.com` or `yum.private.zscaler.com`
- Revert: remove `/opt/zscaler/var/image.bin`, `/opt/zscaler/var/version`, `/opt/zscaler/var/metadata` and restart
- Full rebuild: wipe `/opt/zscaler/var/*` and re-provision
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.
- 12d ago First seen · 97 lines · 25 tokens per session scan B 125a3ebe8df2
troubleshoot-connector is a command published in the GitHub repository zscaler/zscaler-mcp-server (50 stars, last pushed 5d ago), licensed MIT. It adds 25 tokens to every session and 740 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 2 findings (asks for root, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
ui-aqa-flow-test-report-analysis
Phase 7 Test Report Analysis of ui-aqa-flow.
trace-claude-code
Control Opik tracing for your Claude Code sessions.
preflight
Diagnostique l'environnement Cortex et guide la réparation (DB, extensions, modèles).
inventory
Codebase inventory skill — scans the repo for a named pattern (inline SQL, fetch calls, feature flags, debug leftovers, deprecated APIs, etc.) and emits a structured Markdown inventory cross-referenced with framework metadata (routes, handlers). Language-agnostic and pack-driven — the engine matches whatever a YAML…
diagnose
Diagnose why ig-dl isn't working — checks auth, browsers, and backend availability.
checklist
Generate a custom checklist for the current feature based on user requirements.