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/create-access-rule)<a href="https://agentmods.dev/commands/zscaler/zscaler-mcp-server/create-access-rule"><img src="https://agentmods.dev/badge/commands/zscaler/zscaler-mcp-server/create-access-rule.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.00020 | $0.00425 |
| Opus 5 | $0.00010 | $0.00212 |
| Sonnet 5 | $0.00004 | $0.00085 |
| Haiku 4.5 | $0.00002 | $0.00042 |
Grade A, and why
create-access-rule 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
Create ZPA Access Policy Rule
Create rule: $ARGUMENTS
Step 1: Parse Input
Extract:
- Rule name
- Action: ALLOW or DENY
- Application or app group to apply to (optional)
- User, group, or department to apply to (optional)
If insufficient details, ask the administrator what conditions to apply.
Step 2: Look Up Required IDs
For application conditions:
zpa_list_application_segments()
zpa_list_segment_groups()
```text
**For identity conditions:**
```text
zpa_list_scim_groups()
zpa_list_saml_attributes()
```text
## Step 3: Build Conditions
Construct v2 conditions. Common patterns:
**By SCIM group:**
```json
[{"operands": [{"object_type": "SCIM_GROUP", "entry_values": [{"lhs": "<idp_id>", "rhs": "<group_id>"}]}]}]
```text
**By application:**
```json
[{"operands": [{"object_type": "APP", "values": ["<segment_id>"]}]}]
```text
**Combined (group + app):**
Multiple condition objects are AND-ed together.
## Step 4: Create the Rule
```text
zpa_create_access_policy_rule(
name="<rule_name>",
action="<ALLOW|DENY>",
conditions=[...]
)
```text
## Step 5: Verify
```text
zpa_list_access_policy_rules()
```text
Confirm the rule was created, its position in the rule order, and that conditions are correct.
Present a summary with the rule details, noting that rule ordering matters (rules are evaluated top-down, first match wins).
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 · 77 lines · 20 tokens per session scan A e34b58ecdfab
create-access-rule is a command published in the GitHub repository zscaler/zscaler-mcp-server (50 stars, last pushed today), licensed MIT. It adds 20 tokens to every session and 425 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.