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/investigate-url)<a href="https://agentmods.dev/commands/zscaler/zscaler-mcp-server/investigate-url"><img src="https://agentmods.dev/badge/commands/zscaler/zscaler-mcp-server/investigate-url/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/investigate-url"><img src="https://agentmods.dev/badge/commands/zscaler/zscaler-mcp-server/investigate-url.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.00447 |
| Opus 5 | $0.00010 | $0.00224 |
| Sonnet 5 | $0.00004 | $0.00089 |
| Haiku 4.5 | $0.00002 | $0.00045 |
Grade A, and why
investigate-url 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 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.
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
Investigate URL Category
Investigate: $ARGUMENTS
Step 1: Classify the URL
If a URL was provided (not a category name):
zia_url_lookup(urls=["<url>"])
```text
Note the category name and ID.
## Step 2: Search Across All Policy Types
Check every policy type for references to this category:
**URL Filtering:**
```text
zia_list_url_filtering_rules()
```text
**SSL Inspection:**
```text
zia_list_ssl_inspection_rules()
```text
**DLP Web Rules:**
```text
zia_list_dlp_web_rules()
```text
**Cloud Firewall:**
```text
zia_list_cloud_firewall_rules()
```text
## Step 3: Map Policy Impact
For each rule that references the category, document:
- Rule name and order
- Action (ALLOW, BLOCK, CAUTION, INSPECT, DO_NOT_INSPECT, etc.)
- Scope (which users/groups/departments)
- Whether the rule is enabled
## Step 4: Present Report
```text
URL Category Policy Impact Report
===================================
URL: <url>
Category: <category_name>
Referenced in X rules across Y policy types:
URL FILTERING (Z rules):
1. "<rule>" (order N): BLOCK for All Users
2. "<rule>" (order N): ALLOW for <group> (override)
SSL INSPECTION (Z rules):
1. "<rule>" (order N): DO_NOT_INSPECT for All Users
DLP (Z rules):
(none)
CLOUD FIREWALL (Z rules):
1. "<rule>" (order N): ALLOW ports 80,443
Net effect for a typical user:
URL Filtering: BLOCKED
SSL Inspection: NOT INSPECTED
DLP: Not applicable (bypassed by SSL)
```text
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 · 88 lines · 20 tokens per session scan A 64dd548dafa9
investigate-url is a command published in the GitHub repository zscaler/zscaler-mcp-server (50 stars, last pushed 4d ago), licensed MIT. It adds 20 tokens to every session and 447 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.