onboard-app

onboard-app is a command for Claude Code from zscaler/zscaler-mcp-server. It costs 20 tokens per session (449 once invoked), scanned A, original, MIT.

A command for onboarding a new application into ZPA, a system for controlling access to private applications. It gathers the application details and creates or reuses the network resources needed to connect users to it.

In plain words
What is it for?
Adding an application domain and port to ZPA, checking connector groups, and creating the connector, server, segment, and application resources it needs.
Why use it?
It removes the need to manually build each dependency in the required order and checks for existing resources before creating duplicates.

Command for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter.

Part of the zscaler plugin — 42 skills, 20 commands, 1 MCP server shipped together

Good fit Adding an application domain and port to ZPA, checking connector groups, and creating the connector, server, segment, and application resources it needs.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/zscaler/zscaler-mcp-server/onboard-app
Install

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.

Clone the repo
git clone --depth 1 https://github.com/zscaler/zscaler-mcp-server

Made for: Claude Code.

Or install zscaler, the plugin that ships this one along with the rest of its 42 skills, 20 commands, 1 MCP server.

Wrote 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.

agentmods badge for onboard-app

README.md
[![agentmods](https://agentmods.dev/badge/commands/zscaler/zscaler-mcp-server/onboard-app/github.svg)](https://agentmods.dev/commands/zscaler/zscaler-mcp-server/onboard-app)
Your own site
<a href="https://agentmods.dev/commands/zscaler/zscaler-mcp-server/onboard-app"><img src="https://agentmods.dev/badge/commands/zscaler/zscaler-mcp-server/onboard-app/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.

agentmods 80×15 button for onboard-app

Your own site · 80×15
<a href="https://agentmods.dev/commands/zscaler/zscaler-mcp-server/onboard-app"><img src="https://agentmods.dev/badge/commands/zscaler/zscaler-mcp-server/onboard-app.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 20 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 449 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00020 $0.00449
Opus 5 $0.00010 $0.00225
Sonnet 5 $0.00004 $0.00090
Haiku 4.5 $0.00002 $0.00045

Measured 9d ago against content hash d4ad725c6de3, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

onboard-app 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 9d 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.

commands/onboard-app.md · 91 lines

What it actually says

Onboard Application in ZPA

Onboard a new application: $ARGUMENTS

Step 1: Parse Input

Extract:

  • Application name
  • Domain(s) and port(s) (e.g., app.company.com:443)
  • Description (optional)

If domain or port is missing, ask the administrator.

Step 2: Check Existing Resources

zpa_list_application_segments()
```text

Verify no duplicate application segment exists for this domain.

```text
zpa_list_app_connector_groups()
```text

Check if a suitable connector group already exists.

## Step 3: Create Dependencies (if needed)

Follow the ZPA dependency chain:

1. **App Connector Group** (if none suitable):

```text
zpa_create_app_connector_group(name="<name>", location="<location>", country_code="<cc>")
```text

2. **Server Group** referencing the connector group:

```text
zpa_create_server_group(name="<name>", app_connector_group_ids=["<id>"])
```text

3. **Segment Group**:

```text
zpa_create_segment_group(name="<name>")
```text

## Step 4: Create Application Segment

```text
zpa_create_application_segment(
  name="<app_name>",
  domain_names=["<domain>"],
  tcp_port_ranges=["<port>", "<port>"],
  segment_group_id="<id>",
  server_group_ids=["<id>"]
)
```text

## Step 5: Create Access Policy Rule

```text
zpa_create_access_policy_rule(
  name="Allow <app_name>",
  action="ALLOW",
  conditions=[...]
)
```text

Ask the administrator which users/groups should have access.

## Step 6: Verify

```text
zpa_get_application_segment(segment_id="<id>")
```text

Confirm the application segment is enabled and all references are correct.

Present a summary of all created resources with their IDs.
Changes

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.

  1. 9d ago First seen · 91 lines · 20 tokens per session scan A d4ad725c6de3

Subscribe to this mod's changes

onboard-app is a command published in the GitHub repository zscaler/zscaler-mcp-server (50 stars, last pushed 2d ago), licensed MIT. It adds 20 tokens to every session and 449 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.