Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/controlplane-com/ai-pluginnpx agentmods add skills/controlplane-com/ai-plugin/cplnWrote 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/controlplane-com/ai-plugin/cpln)<a href="https://agentmods.dev/skills/controlplane-com/ai-plugin/cpln"><img src="https://agentmods.dev/badge/skills/controlplane-com/ai-plugin/cpln/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/controlplane-com/ai-plugin/cpln"><img src="https://agentmods.dev/badge/skills/controlplane-com/ai-plugin/cpln.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 104 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00062 | $0.06913 |
| Opus 5.5 | $0.00025 | $0.02765 |
| Sonnet 5.5 | $0.00012 | $0.01383 |
| Haiku 4.5 | $0.00006 | $0.00691 |
Grade A, and why
cpln 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 16d 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 — 313 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cpln CLI
MCP first; the CLI covers what the MCP cannot. With the MCP connected, its tools do every operation they cover, reads included; the CLI is for the CLI-only operations below (building a folder on disk among them), interactive debugging, scripted GitOps, and sessions without the MCP. A connected MCP that is signed out means the user signs in again, not a switch to the CLI. In CI/CD the CLI is the primary interface — pipelines authenticate with a service-account key in CPLN_TOKEN, build and push images (cpln image build --push, or --remote on a runner with no Docker daemon), and apply resources (cpln apply --ready). Platform rules (resource model, secrets, destructive ops, production defaults, scale-to-zero, firewall) live in the operating guide (get_cpln_rules); this skill is the CLI mechanics.
Never write a cpln command from memory. Verify every verb and flag with cpln <command> --help before quoting it. If a command isn't in the resource command map below, assume it isn't real.
CLI-only operations
No MCP equivalent — the CLI's primary job:
| Command | Purpose |
|---|---|
cpln image build |
Build a container image — locally with Docker, or on Control Plane with --remote (no daemon) — and push to the org registry |
cpln image copy |
Copy an image between orgs |
cpln port-forward |
Forward local ports to a running workload |
cpln convert |
Convert Kubernetes manifests to Control Plane specs (Compose is cpln stack) |
cpln cp |
Copy files in or out of a running container |
cpln apply |
Scripted GitOps — declarative create-or-update from files |
One-shot and interactive container commands, TTY sessions (workload connect, exec -it), and streamed logs (cpln logs --tail) are also CLI-only; MCP's get_workload_logs covers bounded log fetches. Everything else — discovery and CRUD — prefer the MCP tools (generic mcp__cpln__list_resources / get_resource / delete_resource with a kind, typed create_*/update_* for mutations).
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.
- 16d ago Changed 033e579c4caf
- 17d ago Changed · -16 lines 0b6f9151debb
- 1mo ago First seen · 329 lines · 62 tokens per session scan A 6cde9949dd99
cpln is a skill published in the GitHub repository controlplane-com/ai-plugin (11 stars, last pushed 4d ago), licensed MIT. It adds 62 tokens to every session and 6,913 once invoked, about $0.0002 per session on Opus 5.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
atmos-lint
Atmos Terraform linting with TFLint: standalone atmos terraform lint, component-aware config discovery and toolchain versions, TFLint rule configuration, and lifecycle hooks/CI findings. Use when configuring, running, debugging, or documenting Terraform/OpenTofu linting in an Atmos project.
nx-cloud-ci-failure-review
Requires the nx-cloud-api skill for all Nx Cloud reads. This workflow is read-only.
failure-diagnosis
Diagnose deployment failures, container crashes, and networking issues using structured pattern matching on logs and container state. Use when a deployment fails, a container crashes or exits unexpectedly, or the app is unreachable after deployment.
pstack
Project-local pstack validation router for chmonitor. Use when proving a dashboard, API, auth or security, PeerDB, alerts and webhooks, Helm and GitOps, deployment, or CLI change. Prefer CI checks and capture observable evidence instead of running heavy local builds.
platform-integration
Cross-layer platform integration skill covering end-to-end delivery flows, team onboarding, DORA metrics, cross-layer debugging, and platform health checks. Orchestrates across all platform layers (build, pipeline, registry, secrets, mesh, GitOps, progressive delivery) and owns gitops-promoter CRDs (PromotionStrategy…
diagnosing-azure-deployment-failures
Matches Azure deploy / CI / runtime failures against 56 documented gotchas with verified fixes (BCP258, AADSTS70021, sqlcmd-not-found, FC1-CLI-silent-fallback, functions-action outage, Kudu quick-succession abort, ACS dataLocation quirks, SSE timeouts, Container Apps idle-burn, SWA Authorization-header overwrite, and…