Commonly is a self-hosted collaborative workspace where people work with multiple AI agents, each retaining its own name, memory, skills, and workstation. Teams use it to assign and refine real work across different agent runtimes, and the catalogue entries supply agents, skills, and instructions for use in those rooms.
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 Team-Commonly/commonly --skill pod-chat-tonegit clone --depth 1 https://github.com/Team-Commonly/commonlyWrote 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/team-commonly/commonly/pod-chat-tone)<a href="https://agentmods.dev/skills/team-commonly/commonly/pod-chat-tone"><img src="https://agentmods.dev/badge/skills/team-commonly/commonly/pod-chat-tone/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/team-commonly/commonly/pod-chat-tone"><img src="https://agentmods.dev/badge/skills/team-commonly/commonly/pod-chat-tone.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.00135 | $0.01946 |
| Opus 5.5 | $0.00054 | $0.00778 |
| Sonnet 5.5 | $0.00027 | $0.00389 |
| Haiku 4.5 | $0.00014 | $0.00195 |
Grade A, and why
pod-chat-tone 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 today.
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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pod Chat Tone
Scope: A mandatory rewrite pass before any agent posts a message into a Commonly pod. Applies to every seat — dev agents, wrapper agents, support, guide. Rebuilds the draft as a message to a teammate in a chat room, not a status report pasted into one.
Why this exists (the uncomfortable part)
Measured on our own dev pod, 2026-08-06:
| median agent message | 2,698 characters |
| p90 | 4,591 |
| longest | 6,004 |
| over 1,500 chars | 33 of 40 |
A 2,700-character median in a chat room is a document. Sam's verdict: "agents works are too extensive to consume for human users, the tone and length are too ai like."
This is the same Claude-prose fingerprint the earlier tone work was written to strip, in a different habitat. There the failure was metronome-uniform 275-char replies; here it is 2,700-char essays. Same origin, opposite symptom.
And it is not only style. The dominant defect is subject. Real line from the corpus:
"Convergent crossings need no arbitration; noting it only so the count stays honest."
That is an agent narrating its own coordination protocol at another agent. A human scrolling that pod learns nothing about the product — they are reading minutes of a meeting about the meeting. Agents are performing rigor at each other. Length is downstream of that; fix the subject and most of the length goes with it.
What a pod message is
A pod is a chat room a human might scroll. The reader is a teammate with thirty seconds, not a reviewer auditing your reasoning. Three consequences:
- Post the result, not the trace. The thinking earned the answer; it is not the answer. If the reasoning matters, it goes in the PR body, the ADR, or a linked doc — not the room.
- One message, one thing. If a draft has three bold headers it is three messages, or it is a document with a link.
- Nobody asked for the audit trail. "Stated precisely so it isn't over-read on resume" is a sentence written for a reader who does not exist.
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.
- today First seen · 111 lines · 0 tokens per session scan A 53ee403287fb
pod-chat-tone is a skill published in the GitHub repository Team-Commonly/commonly (1,370 stars, last pushed today), licensed Apache-2.0. It adds 135 tokens to every session and 1,946 once invoked, about $0.0005 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-10-24.
Other skills, from other repositories
social
When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, Facebook, or other platforms, or wants to do social listening and engagement triage. Also use when the user mentions 'LinkedIn post,' 'Twitter thread,' 'social media,' 'content calendar,'…
humanizer
Rewrite AI-sounding text so it reads naturally without changing what it says. Use when editing or reviewing prose for inflated claims, sales language, vague sources, repetitive structure, stock AI words, passive voice, filler, or chatbot artifacts. Based on Wikipedia's "Signs of AI writing.".
seo-audit
When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking,"…
stop-slop
Remove AI writing patterns from prose. Use when drafting, editing, or reviewing text to eliminate predictable AI tells.
b0
Delegate tasks to AI agents via Box0. Use when the user asks to review code, check security, run tests, compare tools, get multiple perspectives, research a topic, analyze data, write docs, or any task that could benefit from specialized or parallel execution. Also use when the user mentions agent names or says "ask"…
intelligence-vocabulary
Locks customer-facing CopilotKit Intelligence docs to one approved name per concept. Use when writing, editing, or reviewing Intelligence docs, nav labels, signup labels, or image alt text in showcase/shell-docs. Don't use for renaming code identifiers, route slugs, env vars, API fields, or component names, or for…