canonical/charm-tech is a shared repository that stores the common standards, decisions, specifications, style guides, and templates used across Canonical Charm Tech repositories. The Charm Tech team uses it as a central source so its repositories can reference or reuse the same documentation, Python and Go conventions, security policies, and CI configuration.
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 skills add canonical/charm-tech --skill cli-standardsgit clone --depth 1 https://github.com/canonical/charm-techWrote 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/canonical/charm-tech/cli-standards)<a href="https://agentmods.dev/skills/canonical/charm-tech/cli-standards"><img src="https://agentmods.dev/badge/skills/canonical/charm-tech/cli-standards/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/canonical/charm-tech/cli-standards"><img src="https://agentmods.dev/badge/skills/canonical/charm-tech/cli-standards.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00044 | $0.01609 |
| Opus 5.5 | $0.00018 | $0.00644 |
| Sonnet 5.5 | $0.00009 | $0.00322 |
| Haiku 4.5 | $0.00004 | $0.00161 |
Grade A, and why
cli-standards 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 1mo 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 — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Canonical CLI Standards
These standards define how Canonical CLI tools should look and behave. They originate from discussions with Canonical's senior tech leads and define best practice. All points must be strongly considered before contributing CLI code at Canonical.
For full do/don't examples of every rule, see examples.md.
Grammar + Vocabulary
Commands are verbs
Every command that acts on a primary object must be a verb (for example: install, refresh, login). Choose verbs that imply the object type they act on.
Commands are logically grouped
Group commands that act on the same object type or domain (for example: build lifecycle vs. store management).
Verb-noun form
When verbs alone are insufficient to distinguish objects, use verb-noun form:
snap set-quota
Listing secondary objects
Use the plural noun as shorthand instead of list-foobar:
snap services # not: snap list-services
snap list # for listing primary objects (snaps)
Showing state
- Use
statusovershow-status - Use
foobar-statusovershow-foobar-status - Use
foobarovershow-foobar
Standard commands
| Command | Purpose |
|---|---|
tool init |
Local initialisation |
tool bootstrap |
Distributed initialisation (cluster, VM, cloud) |
tool list |
Overview of all primary type instances |
tool foobars |
Overview of all secondary type instances |
tool show <id> |
Details for one primary instance |
tool status |
Current tool state |
tool start/stop |
Services, long-running processes |
tool enable/disable |
Primary type, feature |
tool get/set/unset |
Configuration |
tool create-foo <id> |
Create secondary object |
tool delete-foo <id> |
Delete secondary object |
tool help |
Show help |
tool version |
Show release version |
Sublevels
At most one sublevel may be used. Alternatively, split into separate tools with associated names:
cmd cluster config --secret "$(cat secret.txt)"
# OR
cmd-cluster config --secret "$(cat secret.txt)"
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 209 lines · 44 tokens per session scan A ece6028854d3
cli-standards is a skill published in the GitHub repository canonical/charm-tech (4 stars, last pushed 7d ago), licensed Apache-2.0. It adds 44 tokens to every session and 1,609 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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…