Borrowing it
Nothing to install: this file belongs to tatargabor/set-copilot. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/tatargabor/set-copilot/master/.claude/skills/agent-comm/SKILL.mdgit clone --depth 1 https://github.com/tatargabor/set-copilotWrote 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/tatargabor/set-copilot/agent-comm)<a href="https://agentmods.dev/skills/tatargabor/set-copilot/agent-comm"><img src="https://agentmods.dev/badge/skills/tatargabor/set-copilot/agent-comm/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/tatargabor/set-copilot/agent-comm"><img src="https://agentmods.dev/badge/skills/tatargabor/set-copilot/agent-comm.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.00090 | $0.02185 |
| Opus 5.5 | $0.00036 | $0.00874 |
| Sonnet 5.5 | $0.00018 | $0.00437 |
| Haiku 4.5 | $0.00009 | $0.00218 |
Grade A, and why
agent-comm 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Talking to the other sessions
The bus is set-agent-comm: one file per session, everyone appends to their own and reads the
others'. Rooms here: set-copilot.
The one rule everything else follows from
Being read is free. Being interrupted is not. A wake-up is a whole turn of this session, on this model, with this project's context behind it. So the bus separates the two, and it does so in the server rather than in your good intentions:
| what you send | who is interrupted |
|---|---|
anything with to |
exactly those agents |
broadcast QUESTION / REQUEST |
everyone in the room |
broadcast FACT / ANSWER |
nobody — delivered, unread, read when they next look |
This is measured, not guessed. In this bus's first two days, 190 entries were written and every
single one was a broadcast — to was never used, so every entry woke every seat. In one room
that produced 23 entries in 8 minutes between four sessions, each a 2000-character broadcast
FACT, each re:-chained to the last, and the message saying "I'm closing this off" woke everyone
and asked for another answer.
Two habits follow:
- Broadcast a
FACTfreely. It costs the others nothing. This is the cheap, generous move. - When you need an answer, address it.
to: ["<seat>"]— and the seat you want is almost always thefromof the entry you are replying to.
…and one trap that comes with them
⚠ A free FACT is not a free lunch. Measured on 2026-08-06 in a six-session live run: all five
entries were broadcast FACTs, including the one that renamed an id two other projects had to
follow, and a decision that two of them had to agree on. Nobody was woken by any of them. It worked
only because every session happened to be given a turn anyway.
So, before you send: does anyone have to DO something because of this?
- No → broadcast
FACT. Free, and everyone gets it. - Yes, and you know who →
REQUEST(orQUESTION)tothat seat. One name. - Yes, several people, different things → that is one send each, not one entry naming them all.
- Yes, but you do not know who → broadcast
REQUEST. It wakes the room, which is the price of not knowing, andagentsusually answers it first.
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 Changed · +2 lines 2964de826158
- 1mo ago First seen · 165 lines · 90 tokens per session scan A c5dca3290386
agent-comm is a skill published in the GitHub repository tatargabor/set-copilot (3 stars, last pushed 20d ago), licensed MIT. It adds 90 tokens to every session and 2,185 once invoked, about $0.0004 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-09-04.
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…