A guide for deploying a Control Plane wormhole agent, a small service that creates an outbound connection from a private network to Control Plane. This lets workloads reach systems in places such as a VPC, an on-premises data center, or another cloud.

Use it to create and deploy the agent, connect it to a private network, attach the required identity, add network resources, and verify access to the target host.

It avoids exposing private systems directly to the internet and provides the steps to connect workloads to private network endpoints. The connection can carry TCP or UDP traffic.

setup-agent — Skill by controlplane-com

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.

agentmods

npx agentmods add skills/controlplane-com/ai-plugin/setup-agent

Any agent

npx skills add controlplane-com/ai-plugin --skill setup-agent

Clone the repo

git clone --depth 1 https://github.com/controlplane-com/ai-plugin

Made for: Claude Code, Codex.

Per session 50 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,091 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

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.

Model	Per session	Once invoked
Fable 5	$0.00050	$0.02091
Opus 5	$0.00025	$0.01045
Sonnet 5	$0.00010	$0.00418
Haiku 4.5	$0.00005	$0.00209

Measured yesterday against content hash 9316a809427c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

setup-agent 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 yesterday.

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.

plugins/cpln/skills/setup-agent/SKILL.md · 98 lines

How it starts

The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Agent Setup

Tool availability: the agent lifecycle tools — create_agent / update_agent, get_agent_info / get_agent_eventlog, and add_identity_network_resource / add_identity_native_network_resource / remove_identity_network_resource / list_identity_network_resources — live in the full toolset profile. create_identity / update_identity / update_workload and all reads/deletes (list_resources, get_resource, delete_resource) are core. If a full tool is not advertised, reconnect the MCP server with ?toolsets=full, or use the cpln agent CLI.

A wormhole agent is a lightweight VM or container you run inside the target network. It opens a persistent outbound connection to Control Plane and tunnels workload traffic to any TCP/UDP endpoint on the private side — VPC, on-prem, data center, Azure VNet, cross-cloud, or a laptop. A workload reaches the endpoint by attaching an identity (gvc-scoped) that carries a networkResources entry pointing at the agent. No external egress firewall rule is needed.

Scope: this is the deploy walkthrough — create the agent, deploy it on your platform, wire up the identity, verify. For the PrivateLink/PSC-vs-agent comparison, agent sizing tables, the full identity schema, and agent permissions, read native-networking. For the cloud-credential side (AWS/GCP/Azure access without an agent), read setup-cloud-access.

Before you start

Confirm with the user: what private resource the workload must reach (host/IP + ports), where it lives (cloud/VPC/on-prem/cluster), the org, and whether an agent already exists (list_resources kind="agent"). Reach for an agent only when PrivateLink/PSC does not fit — for an AWS or GCP managed service, native networking is lower-latency and needs no agent (see native-networking). An agent is right for on-prem, cross-cloud, Azure, or local development. Check which direction the user means: an agent lets a Control Plane workload reach into their network; it does not run the workload on their hardware. For that — bare metal, on-prem VMs, a data-center server as a deployment target — the answer is a BYOK location (mk8s-byok).

Read the full file on GitHub · 98 lines

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.

yesterday First seen · 98 lines · 50 tokens per session scan A 9316a809427c

Subscribe to this mod's changes

setup-agent is a skill published in the GitHub repository controlplane-com/ai-plugin (10 stars, last pushed 8d ago), licensed MIT. It adds 50 tokens to every session and 2,091 once invoked, about $0.0003 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-31.

DevOps and cloud ai ai-agents claude-code cloud-native codex controlplane

rustfs-release-publish

Run the end-to-end RustFS console gate, version bump, preview validation, human confirmation, and final-tag publication pipeline. Use only when the user explicitly asks to release or publish a RustFS version (发版/发布).

rustfs/rustfs · 52 tokens

pr-review

Review a GitHub PR end-to-end from a URL or number — fetch metadata, inspect the diff, run multi-role adversarial review, check CI status, and post the review comment. Use when the user provides a PR link and asks to review it.

rustfs/rustfs · 55 tokens

issue-triage

Triage a GitHub issue — determine if it is already fixed, needs implementation, or should be closed. Searches related commits and PRs, verifies implementation status, and posts a triage comment or closes the issue. Use when the user provides an issue URL and asks whether it can be closed or needs work.

rustfs/rustfs · 68 tokens

security-advisory-lessons

Perform a dedicated RustFS security/advisory review for authn/authz, IAM, RPC trust, paths, secrets, browser isolation, encryption, Object Lock, or other security boundaries. Use only when the user requests a security/advisory review or an adversarial review explicitly escalates to the full advisory map; do not…

rustfs/rustfs · 83 tokens

tier-debug

Debug ILM tiering / lifecycle transition issues — NoSuchVersion on tier GET, restore failures, xl.meta inspection, remote-tier versionId tracing. Use when investigating tiered/transitioned objects, warm backends, or transition metadata.

rustfs/rustfs · 51 tokens

plugin-contract-guard

Invariants and change procedure for the target-plugin / extension system — plugin manifests, admin plugin/extension catalog and instance APIs, secret redaction, external-plugin install policy. Use when editing crates/targets (manifest, plugin, controlplane, catalog, runtime), crates/extension-schema, or…