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 skills/controlplane-com/ai-plugin/org-managementnpx skills add controlplane-com/ai-plugin --skill org-managementgit clone --depth 1 https://github.com/controlplane-com/ai-pluginWhat 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.02915 |
| Opus 5 | $0.00025 | $0.01458 |
| Sonnet 5 | $0.00010 | $0.00583 |
| Haiku 4.5 | $0.00005 | $0.00292 |
Grade A, and why
org-management 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 2d 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Organization & User Management
An org is the top-level isolation boundary: every GVC, workload, secret, policy, image, domain, user, group, and service account lives inside one, with no cross-org sharing. An org cannot be renamed or deleted once created (every DELETE on /org returns 405) and its name is globally unique across all of Control Plane — so the first job is choosing a name you can live with permanently.
Tool availability: the org-settings, group, service-account, and invite tools live in the
fullMCP toolset; onlylist_quotasand the genericlist_resources/get_resource/delete_resourcereads are incore. If a tool below is not advertised, reconnect with?toolsets=fullor use thecplnCLI fallback.
Organization
| Rule | Detail |
|---|---|
| Name charset | Lowercase letters, digits, hyphens; must start with a letter, cannot end with a hyphen; max 64 chars |
| Reserved names | Cannot be index; cannot start with xserve- |
| Uniqueness | Globally unique across the whole platform (DB-enforced), not per billing account |
| Immutability | Name is unmodifiable; the org cannot be deleted — plan the name carefully |
Create an org (requires the org_creator or billing_admin role on a billing account — enforced by the billing service, not org policy):
cpln org create --name ORG --accountId BILLING_ACCOUNT_ID \
--invitee [email protected] --invitee [email protected]
--name, --accountId, and --invitee (repeatable) are all required; invitees join the superusers group. Optional: --description, --tag key=value. Console path: Create, then Org. The first billing account can only be created in the Console.
Org-wide settings
Read with mcp__cpln__get_resource (kind org); change with mcp__cpln__update_org (a merge/PATCH — pass only the blocks you change). Settings apply to every member and workload.
| Spec block | Set via update_org? |
Notes |
|---|---|---|
sessionTimeoutSeconds |
Yes | Console inactivity timeout; minimum 900 (15 min); no platform default |
authConfig.domainAutoMembers |
Yes | Email domains whose users auto-join the org |
authConfig.samlOnly |
Yes | Boolean, no default (unset = off); require SAML for all members |
observability.*RetentionDays |
Yes | logs/metrics/traces, 0–3650, default 30; 0 turns that stream off |
observability.defaultAlertEmails |
Yes | Default Grafana alert recipients |
security.threatDetection |
Yes | Forward detected threats to a syslog target (enabled + optional minimumSeverity + syslog host/port) |
logging / extraLogging |
No | Use mcp__cpln__configure_external_logging — see external-logging |
tracing |
No | Escape hatch: mcp__cpln__get_resource_schema (kind org), author the block, cpln apply -f org.yaml |
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.
- 2d ago First seen · 159 lines · 50 tokens per session scan A b28c5d935d18
org-management 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,915 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.
Other skills, from other repositories
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 (发版/发布).
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.
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.
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…
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.
nginx-to-higress-migration
Migrate from ingress-nginx to Higress in Kubernetes environments. Use when (1) analyzing existing ingress-nginx setup (2) reading nginx Ingress resources and ConfigMaps (3) installing Higress via helm with proper ingressClass (4) identifying unsupported nginx annotations (5) generating WASM plugins for nginx…