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.
npx agentmods add commands/zscaler/zscaler-mcp-server/create-timeout-rulegit 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-timeout-rule)<a href="https://agentmods.dev/commands/zscaler/zscaler-mcp-server/create-timeout-rule"><img src="https://agentmods.dev/badge/commands/zscaler/zscaler-mcp-server/create-timeout-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 | $0.00021 | $0.00315 |
| Opus 5 | $0.00010 | $0.00158 |
| Sonnet 5 | $0.00004 | $0.00063 |
| Haiku 4.5 | $0.00002 | $0.00032 |
Grade A, and why
create-timeout-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 5d 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 Timeout Policy Rule
Create timeout rule: $ARGUMENTS
Step 1: Parse Input
Extract:
- Rule name
- Re-authentication timeout in seconds (e.g., 86400 = 24 hours)
- Idle timeout in seconds (optional, e.g., 1800 = 30 minutes)
- Application or group scope (optional)
Step 2: Look Up Application IDs (if scoped)
zpa_list_application_segments()
zpa_list_segment_groups()
```text
## Step 3: Build Conditions
If scoped to specific applications:
```json
[{"operands": [{"object_type": "APP", "values": ["<segment_id>"]}]}]
```text
## Step 4: Create the Rule
```text
zpa_create_timeout_policy_rule(
name="<rule_name>",
reauth_timeout=<seconds>,
reauth_idle_timeout=<idle_seconds>,
conditions=[...]
)
```text
## Step 5: Verify
```text
zpa_list_timeout_policy_rules()
```text
Present summary with rule details and human-readable timeout values (e.g., "24 hours re-auth, 30 minutes idle").
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.
- 5d ago First seen · 54 lines · 21 tokens per session scan A f6c41ccfc910
create-timeout-rule is a command published in the GitHub repository zscaler/zscaler-mcp-server (50 stars, last pushed 11d ago), licensed MIT. It adds 21 tokens to every session and 315 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
epic-decompose
Break epic into concrete, actionable tasks.
issue-sync
Push local updates as GitHub issue comments for transparent audit trail.
create
This command creates the initial project context documentation in .claude/context/ by analyzing the current project state and establishing comprehensive baseline documentation.
epic-start
Launch parallel agents to work on epic tasks in a shared branch.
prd-parse
Convert PRD to technical implementation epic.
prime
This command loads essential context for a new agent session by reading the project context documentation and understanding the codebase structure.