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 skills add zscaler/zscaler-mcp-server --skill application_segment-pra-onboardgit 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/skills/zscaler/zscaler-mcp-server/application_segment-pra-onboard)<a href="https://agentmods.dev/skills/zscaler/zscaler-mcp-server/application_segment-pra-onboard"><img src="https://agentmods.dev/badge/skills/zscaler/zscaler-mcp-server/application_segment-pra-onboard/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/skills/zscaler/zscaler-mcp-server/application_segment-pra-onboard"><img src="https://agentmods.dev/badge/skills/zscaler/zscaler-mcp-server/application_segment-pra-onboard.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.00174 | $0.03990 |
| Opus 5 | $0.00087 | $0.01995 |
| Sonnet 5 | $0.00035 | $0.00798 |
| Haiku 4.5 | $0.00017 | $0.00399 |
Grade A, and why
zpa-application_segment-pra-onboard 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 3d 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 — 409 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ZPA: Onboard Privileged Remote Access (PRA) Application
Keywords
privileged remote access, pra, rdp access, ssh access, jump host, bastion host, jumpbox, pra portal, pra credential, agentless rdp, agentless ssh, browser rdp, browser ssh, secure remote access
Overview
Onboard a new Privileged Remote Access (PRA) application in Zscaler Private Access. PRA segments publish RDP and SSH targets to authorized users through Zscaler's PRA portal — the end user connects through their browser without a native RDP/SSH client and without ZCC. The connection is brokered by the PRA portal and authenticated using PRA credentials managed as separate ZPA resources.
This skill walks through the full dependency chain: connector group → server group → segment group → PRA credential → PRA portal → PRA application segment with apps_config → access policy rule.
Use this skill when: The admin explicitly mentions Privileged Remote Access, PRA, RDP, SSH, jump host, bastion, or "publish a Windows/Linux server for browser-based remote access."
DO NOT use this skill when:
- The admin wants a regular client-routed application segment (any TCP/UDP app reachable via ZCC) — use
zpa-application_segment-onboardinstead. - The admin wants to publish a clientless web application — use
zpa-application_segment-ba-onboardinstead.
What makes PRA different from a regular or BA app segment
| Concept | Regular segment | Browser Access (BA) | Privileged Remote Access (PRA) |
|---|---|---|---|
| SDK / tool family | zpa_*_application_segment |
zpa_*_application_segment_ba |
zpa_*_application_segment_pra |
| Client requirement | ZCC | Browser only | Browser only (via PRA portal) |
| Per-app config block | none | common_apps_dto.apps_config (per domain) |
common_apps_dto.apps_config (per RDP/SSH target) |
Per-app application_protocol |
n/a | HTTP / HTTPS |
RDP / SSH |
| Per-app TLS cert | n/a | certificate_id required |
n/a |
| RDP-only field | n/a | n/a | connection_security (ANY, NLA, NLA_EXT, TLS, VM_CONNECT, RDP) |
Auto-injected app_types |
n/a | BROWSER_ACCESS |
SECURE_REMOTE_ACCESS |
| Update-diff field | n/a | deleted_ba_apps |
deleted_pra_apps |
| Auth to the target | client supplies creds | n/a (web SSO) | PRA credential (managed as pra_credential) bound to the user via the access policy |
| Portal | n/a | n/a | PRA portal (pra_portal) — the URL users connect to |
| Typical port | any TCP/UDP | TCP 443 / 80 | TCP+UDP 3389 (RDP) or TCP 22 (SSH) |
| Access-policy operand type | APP |
APP |
APP — same |
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.
- 3d ago First seen · 409 lines · 174 tokens per session scan A ecdd60f0d4c8
zpa-application_segment-pra-onboard is a skill published in the GitHub repository zscaler/zscaler-mcp-server (50 stars, last pushed 3d ago), licensed MIT. It adds 174 tokens to every session and 3,990 once invoked, about $0.0009 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-09-07.
Other skills, from other repositories
jmcomic
Search, browse, inspect album-specific or site-wide comments, and download manga from JMComic (18comic), obtain the latest Android APK from hect0x7/JMComic-APK, and invoke the upstream jm-view-server jms command for local reading. Use for manga discovery, ranking, comment analysis, downloads, post-processing…
chrome-devtools-cli
Use this skill to write shell scripts or run shell commands to automate tasks in the browser or otherwise use Chrome DevTools via CLI.
a11y-debugging
Uses Chrome DevTools MCP for accessibility (a11y) debugging and auditing based on web.dev guidelines. Use when testing semantic HTML, ARIA labels, focus states, keyboard navigation, tap targets, and color contrast.
chrome-devtools
Uses Chrome DevTools via MCP for efficient debugging, troubleshooting and browser automation. Use when debugging web pages, automating browser interactions, analyzing performance, or inspecting network requests. This skill does not apply to --slim mode (MCP configuration).
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
memory-leak-debugging
Diagnoses and resolves memory leaks in JavaScript/Node.js applications. Use when a user reports high memory usage, OOM errors, or wants to capture, compare, or inspect heap snapshots with Chrome DevTools MCP memory tools.