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/tagnpx skills add controlplane-com/ai-plugin --skill taggit 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.00045 | $0.02488 |
| Opus 5 | $0.00023 | $0.01244 |
| Sonnet 5 | $0.00009 | $0.00498 |
| Haiku 4.5 | $0.00005 | $0.00249 |
Grade A, and why
tag 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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tags — Labeling, Built-in Behaviors & Targeting
Tags are key-value labels on almost every Control Plane resource (workload, GVC, identity, secret, policy, group, domain, image, volumeset, agent, ipset, org, mk8s, user, service account). They live in a top-level tags: map. A tag is three things at once: metadata for humans, a selector that policies/groups/GVCs/queries target, and — under the reserved cpln/ namespace — a switch that turns on platform behavior the spec doesn't yet expose as a field.
Why tags pay off
| Capability | What a tag unlocks | Mechanism |
|---|---|---|
| Dynamic RBAC | A policy targetQuery on environment=production grants on every match — including resources created later |
access-control |
| Dynamic group membership | A group memberQuery auto-enrolls users by tag (e.g. SSO provider) |
access-control |
| Dynamic placement | A GVC locationQuery picks locations by tag (e.g. cpln/country) instead of a fixed list |
query-spec |
| Fleet inventory & bulk ops | cpln KIND query --tag tier=frontend finds every matching resource to act on |
cpln |
| Built-in behaviors | Reserved cpln/* tags switch on features (protection, sticky sessions, mTLS, …) |
see below |
| Console organization | List columns, custom logos, saved groups, and the Query filter all read tags | see below |
The payoff is retroactive and self-maintaining: tag a new workload environment=production and every prod policy, group, and dashboard that queries that tag covers it automatically — no rule edits.
Setting tags
| Where | How |
|---|---|
| CLI, dedicated | cpln KIND tag NAME --tag key=value (repeatable); --remove-tag key drops one |
| CLI, on create | cpln KIND create ... --tag key=value |
| CLI, generic update | cpln KIND update NAME --set tags.key=value (kinds with no tag subcommand, e.g. user) |
| MCP | The mcp__cpln__create_* / update_* tool for the kind accepts a tags object |
| Manifest | A top-level tags: map, then cpln apply -f FILE |
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 · 150 lines · 45 tokens per session scan A 227982915aee
tag is a skill published in the GitHub repository controlplane-com/ai-plugin (10 stars, last pushed 8d ago), licensed MIT. It adds 45 tokens to every session and 2,488 once invoked, about $0.0002 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.
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…