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/review-attack-surface)<a href="https://agentmods.dev/commands/zscaler/zscaler-mcp-server/review-attack-surface"><img src="https://agentmods.dev/badge/commands/zscaler/zscaler-mcp-server/review-attack-surface.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.00027 | $0.00443 |
| Opus 5 | $0.00014 | $0.00221 |
| Sonnet 5 | $0.00005 | $0.00089 |
| Haiku 4.5 | $0.00003 | $0.00044 |
Grade A, and why
review-attack-surface 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
Review Attack Surface
Review attack surface: $ARGUMENTS
Step 1: List Organizations
easm_list_organizations()
```text
If an organization was specified, find its ID. Otherwise, use the primary organization.
## Step 2: Retrieve Findings
```text
easm_list_findings(organization_id="<id>")
```text
## Step 3: Analyze Findings by Severity
Categorize findings:
- **Critical**: Exploitable vulnerabilities, exposed admin panels, default credentials
- **High**: Exposed services (RDP, SSH, databases), expired certificates
- **Medium**: Misconfigurations, information disclosure
- **Low**: Best-practice improvements
## Step 4: Check Lookalike Domains
```text
easm_list_lookalike_domains(organization_id="<id>")
```text
Flag domains that could be used for phishing or brand impersonation.
## Step 5: Get Detailed Finding Info
For critical/high findings:
```text
easm_get_finding(finding_id="<id>")
```text
## Step 6: Present Report
```text
External Attack Surface Report
================================
Organization: <name>
Scan date: <date>
FINDINGS SUMMARY:
Critical: X
High: Y
Medium: Z
Low: W
CRITICAL FINDINGS:
1. <finding_type>: <asset>
Risk: <description>
Remediation: <steps>
HIGH FINDINGS:
1. ...
LOOKALIKE DOMAINS:
- <domain> (similarity: X%) -- potential phishing
- <domain> (similarity: Y%) -- registered <date>
PRIORITY REMEDIATION:
1. <most urgent action>
2. <next action>
```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.
- 8d ago First seen · 82 lines · 27 tokens per session scan A a5316f0c8f33
review-attack-surface is a command published in the GitHub repository zscaler/zscaler-mcp-server (50 stars, last pushed today), licensed MIT. It adds 27 tokens to every session and 443 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.
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.
scan-secrets
Scan the current project for hardcoded secrets and offer to auto-fix them.
primer
Start with reading the CLAUDE.md file if it exists to get an understanding of the project.