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/audit-ssl)<a href="https://agentmods.dev/commands/zscaler/zscaler-mcp-server/audit-ssl"><img src="https://agentmods.dev/badge/commands/zscaler/zscaler-mcp-server/audit-ssl.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.00039 | $0.00612 |
| Opus 5 | $0.00019 | $0.00306 |
| Sonnet 5 | $0.00008 | $0.00122 |
| Haiku 4.5 | $0.00004 | $0.00061 |
Grade A, and why
audit-ssl 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.
How it starts
The opening of the file, as written. The whole thing — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audit SSL Inspection Rules
Audit SSL inspection: $ARGUMENTS
Scope
This command works EXCLUSIVELY with SSL inspection rules. Do NOT call URL filtering, DLP, firewall, or any other non-SSL tools unless the user explicitly asks for cross-referencing.
Step 1: Retrieve SSL Inspection Rules
zia_list_ssl_inspection_rules()
```text
## Step 2: Filter and Categorize
Categorize each rule by its action:
- **INSPECT / DECRYPT** -- traffic is fully decrypted and inspected
- **DO_NOT_INSPECT** -- traffic is not decrypted or inspected (full bypass)
- **DO_NOT_DECRYPT** -- traffic is not decrypted but metadata is visible
- **BLOCK** -- traffic is blocked at the SSL layer
Filter results based on the user's question. If they ask about "decryption mode," show only INSPECT/DECRYPT rules. If they ask about "bypasses," show DO_NOT_INSPECT and DO_NOT_DECRYPT rules.
## Step 3: Analyze Rule Details
For each relevant rule, present:
- Rule name, order, enabled status
- URL categories and cloud applications affected
- Users, groups, departments, locations scoped
- Platforms and device trust levels
Resolve IDs to names only when needed:
```text
get_zia_user_groups(search="<name>")
get_zia_user_departments(search="<name>")
zia_list_locations()
```text
## Step 4: Risk Assessment (bypass audits only)
If auditing bypasses, classify by risk:
- **Critical**: Broad categories (Uncategorized, Miscellaneous), all users, AI/ML apps bypassed
- **High**: Sensitive cloud apps, large departments bypassed
- **Medium**: Certificate-pinning exceptions, narrow user scope
- **Low**: OS updates, system services, high-trust device scoping
## Step 5: Present Report
Organize findings to directly answer the user's question. Include:
- Summary counts by action type
- Detailed rule list (filtered to what the user asked about)
- Risk assessment and recommendations (for bypass audits)
## Important: Do NOT Call These Tools
Unless the user explicitly asks for DLP or URL filtering cross-reference:
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 · 75 lines · 39 tokens per session scan A c567299177ad
audit-ssl is a command published in the GitHub repository zscaler/zscaler-mcp-server (50 stars, last pushed today), licensed MIT. It adds 39 tokens to every session and 612 once invoked, about $0.0002 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.