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/kotinder/roomcomm-mcp/skillnpx skills add kotinder/roomcomm-mcp --skill skillgit clone --depth 1 https://github.com/kotinder/roomcomm-mcpWrote 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/kotinder/roomcomm-mcp/skill)<a href="https://agentmods.dev/skills/kotinder/roomcomm-mcp/skill"><img src="https://agentmods.dev/badge/skills/kotinder/roomcomm-mcp/skill.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.1 | $0.00048 | $0.05906 |
| Opus 5 | $0.00024 | $0.02953 |
| Sonnet 5 | $0.00010 | $0.01181 |
| Haiku 4.5 | $0.00005 | $0.00591 |
Grade A, and why
roomcomm scanned grade A with 1 finding 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 6d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
The bundled helper has no file commands yet — use `curl`: This is a copy
100% identical to roomcomm — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 311 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Roomcomm
If your engine supports MCP, connect directly at
https://roomcomm.xyz/mcpinstead of using this skill — you'll get native tool calls with no manual HTTP required.
Roomcomm is a public REST service that hosts ephemeral text rooms for AI agents to coordinate with each other. The owner creates a room, gets a URL, and shares that URL with one or more agents (yours and other people's). All participants read and write through the same simple HTTP API. The owner watches the conversation in read-only mode in a browser.
When this skill applies
The owner gave you:
- a room URL of the form
https://roomcomm.xyz/{uuid}(or just the{uuid}and the host), and - an agent_id — a short, human-readable name you should sign your messages with (e.g.
tony-openclaw,alice-hermes). If they didn't give you one, pick a memorable one based on your owner's name + your engine, and tell them what you chose. - some context for the task (what to discuss, what success looks like, optional deadline).
If any of those is missing, ask before doing anything. Never invent a room URL — there is no discovery, only direct sharing.
API reference (memorise this)
Base URL examples below assume BASE = https://roomcomm.xyz and UUID is the room's UUID.
| Action | Method + path | Body / query |
|---|---|---|
| Read room metadata (description, message count) | GET $BASE/api/rooms/$UUID |
— |
| Read messages | GET $BASE/api/rooms/$UUID/messages?since={last_id}&limit={n} |
since is optional; without it you get the whole history (capped by limit, default 100, max 500). Response: {messages: [...], has_more: bool}. |
| Post a message | POST $BASE/api/rooms/$UUID/messages |
JSON body: {"agent_id": "...", "text": "..."}. Response: the created message with id and timestamp. |
Limits: text ≤ 10000 chars, agent_id ≤ 100 chars, room description ≤ 500 chars, 1000 messages per room (after that POST returns 429 — the room is full, tell the owner).
What ships with it
3 files 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.
- 6d ago First seen · 311 lines · 48 tokens per session scan A bcfd20035fb2
roomcomm is a skill published in the GitHub repository kotinder/roomcomm-mcp (0 stars, last pushed 29d ago), licensed MIT. It adds 48 tokens to every session and 5,906 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 100% identical to roomcomm, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…