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/query-specnpx skills add controlplane-com/ai-plugin --skill query-specgit 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.00048 | $0.01631 |
| Opus 5 | $0.00024 | $0.00816 |
| Sonnet 5 | $0.00010 | $0.00326 |
| Haiku 4.5 | $0.00005 | $0.00163 |
Grade A, and why
query-spec 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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Query Spec — Filtering & Selecting Resources
Control Plane has one query language used in two ways: ad-hoc filtering of a resource list (CLI / API), and dynamic targeting embedded inside three resource fields.
| Where | Field / command | Purpose |
|---|---|---|
| Policy | targetQuery |
Target resources by tag/property instead of listing targetLinks (see access-control) |
| Group | memberQuery |
Assign members dynamically — users only |
| GVC | spec.staticPlacement.locationQuery |
Select locations dynamically instead of listing locationLinks |
| CLI | cpln KIND query |
Ad-hoc filtering — every resource kind |
| API | POST /org/ORG/KIND/-query |
Ad-hoc filtering — every resource kind |
Not an MCP list parameter. list_resources has no filter argument (list a kind, then filter the table yourself); query_audit_events filters by kind/name/subject/context/time; query_metrics takes PromQL. The query spec appears only inside the three resource fields above, set when you create or update that resource.
Structure
kind: workload # resource kind being selected
fetch: items # "items" (objects, default) or "links" (references)
spec:
match: all # "all" (default), "any", or "none"
terms:
- op: "="
tag: environment
value: production
- op: exists
tag: monitored
sort:
by: name
order: asc
Terms
Each term targets exactly one of three fields (mutually exclusive — the schema rejects a term that sets more than one):
| Field | Targets | Example |
|---|---|---|
tag |
Resource tags (key/value labels) | tag: environment, value: production |
property |
Built-in properties (name, description, status.phase, …) |
property: name, value: my-app |
rel |
Relationships to other resources | rel: gvc, value: my-gvc |
Operators
| Operator | Needs value |
Meaning |
|---|---|---|
= |
yes | Equal (default when op is omitted) |
!= |
yes | Not equal |
> >= < <= |
yes | Numeric / date comparison |
~ |
yes | Pattern match (schema op name match) |
=~ |
yes | Regex match (schema op name regex) |
contains |
yes | Substring match |
exists |
no | Tag/property is present (any value) |
!exists |
no | Tag/property is absent |
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 · 163 lines · 48 tokens per session scan A 265023fdd975
query-spec is a skill published in the GitHub repository controlplane-com/ai-plugin (10 stars, last pushed 8d ago), licensed MIT. It adds 48 tokens to every session and 1,631 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…