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/lexfrei/ccc/etiquettenpx skills add lexfrei/ccc --skill etiquettegit clone --depth 1 https://github.com/lexfrei/cccWrote 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/lexfrei/ccc/etiquette)<a href="https://agentmods.dev/skills/lexfrei/ccc/etiquette"><img src="https://agentmods.dev/badge/skills/lexfrei/ccc/etiquette.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.01591 |
| Opus 5 | $0.00000 | $0.00796 |
| Sonnet 5 | $0.00000 | $0.00318 |
| Haiku 4.5 | $0.00000 | $0.00159 |
Grade A, and why
etiquette 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 4d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kernel lists are a public workspace with strong, mostly unwritten-until-violated norms. This skill is the reference: consult the relevant section, apply it, and when a rule here conflicts with a subsystem's own Documentation/process/maintainer-*.rst, the subsystem wins.
The medium
Everything sent to a list is public, archived on lore.kernel.org forever, quoted in commit messages, and indexed by search engines. English only. Plain text only — no HTML, no attachments, no images; hard-wrapped at about 72 columns. Nothing confidential, no internal infrastructure details, no employer boilerplate footers. Write every mail knowing it may be read ten years later by someone with no context but the thread.
Who to write to
The MAINTAINERS file is the routing table; scripts/get_maintainer.pl reads it for you (feed it patch files, or a file path with --file). When reading an entry directly:
M:— maintainers: the people who take the patch; they go in ToR:— designated reviewers: Cc themL:— the subsystem list: Cc, mandatory — this is where review actually happensS:— status:Maintained/Supportedwill answer;Odd Fixes/Orphanexplains silence in advanceT:— the git tree patches land in; base your work on it, not on Linus' treeP:— subsystem profile document with local rules (tree prefixes, timing); read it before first contactB:— where bugs go, when it is not the list
Routing rules:
- Patches and review questions: maintainers in To, list plus reviewers in Cc,
[email protected]as archive Cc. Review happens on the list; mailing a maintainer privately about an ordinary patch wastes the one reviewer it reaches and is quietly resented. - Bug reports: the subsystem list plus its maintainers, same routing as a patch for the file that misbehaves. A regression (something that worked in a previous kernel) additionally Cc's
[email protected]and names the last good version — bisect first if at all possible. - Security bugs:
[email protected]privately, never the public list, never a public tracker. - Usage questions ("how do I configure X") do not belong on development lists at all.
- A newcomer question is fine on the subsystem list if it shows the homework: what was read, what was tried, where it diverged from expectation.
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.
- 4d ago First seen · 75 lines · 0 tokens per session scan A 94514c980d8b
etiquette is a skill published in the GitHub repository lexfrei/ccc (9 stars, last pushed 2d ago), licensed BSD-3-Clause. It costs nothing until one of its globs matches a file; then it loads 1,591 tokens. 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…