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-incident)<a href="https://agentmods.dev/commands/zscaler/zscaler-mcp-server/investigate-incident"><img src="https://agentmods.dev/badge/commands/zscaler/zscaler-mcp-server/investigate-incident/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-incident"><img src="https://agentmods.dev/badge/commands/zscaler/zscaler-mcp-server/investigate-incident.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.00027 | $0.00499 |
| Opus 5 | $0.00014 | $0.00249 |
| Sonnet 5 | $0.00005 | $0.00100 |
| Haiku 4.5 | $0.00003 | $0.00050 |
Grade A, and why
investigate-incident 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 11d 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 Security Incident
Investigate: $ARGUMENTS
Step 1: Parse Input
Extract:
- Threat type or keyword (e.g., "malware", "phishing", "ransomware", a specific IP or domain)
- Time window in hours (default: 24)
Step 2: Check Threat Categories
zins_get_threat_categories()
```text
Identify the most active threat categories in the environment.
## Step 3: Get Cyber Incident Data
```text
zins_get_cyber_incidents()
```text
Look for incidents matching the threat type or keyword.
## Step 4: Analyze Firewall Actions
```text
zins_get_firewall_actions()
zins_get_firewall_insights()
```text
Check for blocks, allows, and suspicious connection patterns.
## Step 5: Review Web Traffic Patterns
```text
zins_get_web_traffic_overview()
zins_get_web_application_usage()
```text
Look for unusual traffic spikes or suspicious application usage.
## Step 6: Check Shadow IT
```text
zins_get_shadow_it_summary()
zins_get_saas_security_posture()
```text
Identify unsanctioned applications that may have been used in the incident.
## Step 7: Present Investigation Report
```text
Security Incident Investigation
==================================
Timeframe: <start> to <end>
Focus: <threat_type>
THREAT SUMMARY:
Active threat categories: <list>
Incidents detected: X
Firewall blocks: Y
INCIDENT TIMELINE:
<chronological list of events>
AFFECTED ASSETS:
Users: <list>
Devices: <list>
Applications: <list>
FIREWALL ANALYSIS:
Blocked connections: X
Allowed suspicious: Y (review needed)
SHADOW IT FINDINGS:
Unsanctioned apps detected: <list>
ROOT CAUSE ASSESSMENT:
<analysis>
RECOMMENDED ACTIONS:
1. <immediate action>
2. <containment action>
3. <follow-up investigation>
```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.
- 11d ago First seen · 99 lines · 27 tokens per session scan A 86fea8387907
investigate-incident is a command published in the GitHub repository zscaler/zscaler-mcp-server (50 stars, last pushed 4d ago), licensed MIT. It adds 27 tokens to every session and 499 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.