chatroom

chatroom is a skill for Claude Code from ctb111/claude-agent-chatroom. It costs 34 tokens per session (1,416 once invoked), scanned A, original, MIT.

A real-time chat space for coordinating several software agents and the user. It is meant for quick questions, progress updates, and coordination while parallel work is underway.

In plain words
What is it for?
Use it when starting parallel agents that need to exchange information or when you want to monitor their activity. It opens a local chatroom interface for that coordination.
Why use it?
It gives agents a shared place to communicate during a multi-agent task, reducing the need to pass every small update through the main conversation.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: reads .claude/ paths.

Part of the agent-chatroom plugin — 1 skill shipped together

Good fit Use it when starting parallel agents that need to exchange information or when you want to monitor their activity. It opens a local chatroom interface for that coordination.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ctb111/claude-agent-chatroom/chatroom
Install

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.

Any agent
npx skills add ctb111/claude-agent-chatroom --skill chatroom
Clone the repo
git clone --depth 1 https://github.com/ctb111/claude-agent-chatroom

Made for: Claude Code.

Or install agent-chatroom, the plugin that ships this one along with the rest of its 1 skill.

Wrote 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.

agentmods badge for chatroom

README.md
[![agentmods](https://agentmods.dev/badge/skills/ctb111/claude-agent-chatroom/chatroom/github.svg)](https://agentmods.dev/skills/ctb111/claude-agent-chatroom/chatroom)
Your own site
<a href="https://agentmods.dev/skills/ctb111/claude-agent-chatroom/chatroom"><img src="https://agentmods.dev/badge/skills/ctb111/claude-agent-chatroom/chatroom/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.

agentmods 80×15 button for chatroom

Your own site · 80×15
<a href="https://agentmods.dev/skills/ctb111/claude-agent-chatroom/chatroom"><img src="https://agentmods.dev/badge/skills/ctb111/claude-agent-chatroom/chatroom.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 34 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,416 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00034 $0.01416
Opus 5 $0.00017 $0.00708
Sonnet 5 $0.00007 $0.00283
Haiku 4.5 $0.00003 $0.00142

Measured 10d ago against content hash 581dc6dfa2c4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

chatroom 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 10d 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.

skills/chatroom/SKILL.md · 143 lines

How it starts

The opening of the file, as written. The whole thing — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Agent Chatroom

This skill starts a real-time chatroom for coordination between parallel agents and the user. The chatroom is for quick communication, asking questions, and getting help - not for posting work output or results.

Starting the Chatroom

When this skill is invoked, you MUST:

  1. Find the plugin root - look for the agent-chatroom plugin in the enabled plugins list or use this path:

    • macOS/Linux: ~/.claude/plugins/*/agent-chatroom or the cloned repo location
    • The plugin root contains spawn-terminal.js and ui.js
  2. Start the chatroom server/UI by running:

    node <plugin-root>/spawn-terminal.js <plugin-root>/ui.js
    
  3. Wait for the server to be ready (check port 3030):

    nc -z localhost 3030 && echo "Ready" || echo "Starting..."
    
  4. Confirm to the user that the chatroom is open.

Agent Instructions

After starting the chatroom, whenever you spawn agents (using the Task tool):

  • ALWAYS use run_in_background: true so agents run independently
  • MUST append the chatroom instructions below to each agent's prompt
## ⛔ CRITICAL: NEVER RETURN TEXT - IT DISCONNECTS YOU ⛔

**THIS IS THE MOST IMPORTANT RULE:**
- You must NEVER return/output a text response directly
- Returning text = completing your task = disconnecting from the team
- If you want to report ANYTHING, use `chatroom_broadcast` tool instead
- Your ONLY allowed outputs are TOOL CALLS
- Every response you give MUST end with a tool call (chatroom_check, chatroom_broadcast, or work tools)

**WHY:** When you return text without a tool call, you EXIT and disconnect. The team loses you.

**CORRECT behavior:**
- Starting work? → `chatroom_status(name: "yourname", status: "busy", task: "Reading auth.ts")`
- Finished work? → `chatroom_status(name: "yourname", status: "idle")`
- Want to report something? → `chatroom_broadcast(message: "Found the bug!", name: "yourname")`
- Nothing to do? → `chatroom_check(name: "yourname")` (and keep checking every 20 seconds)

**WRONG behavior (NEVER DO THIS):**
- Returning "Here's my status report..."
- Returning "I've completed the task..."
- Returning any text without a tool call

## Chatroom Instructions

You have access to a real-time chatroom for **coordination only**.

**At start:**
- Call `chatroom_join` with your agent name

**During work:**
- **Before starting work:** Call `chatroom_status(name: "yourname", status: "busy", task: "what you're doing")`
- **After finishing work:** Call `chatroom_status(name: "yourname", status: "idle")`
- Call `chatroom_broadcast(message: "...", name: "yourname")` for questions and important updates
- Call `chatroom_check(name: "yourname")` every 15-30 seconds to see messages
- Use other tools (Read, Edit, Bash, etc.) for your actual work
- **IMPORTANT:** Always include your `name` parameter on ALL chatroom calls

**Chatroom etiquette:**
- Brief messages only (like Slack)
- No code dumps or verbose logs
- Ask questions, coordinate, report blockers

## Your Work Loop (MANDATORY)

You MUST follow this pattern FOREVER:

INFINITE LOOP:

  1. chatroom_check(name: "yourname") - look for new messages/instructions
  2. If you have work to do: a. chatroom_status(name: "yourname", status: "busy", task: "description") b. Do the work (Read, Edit, Bash, etc.) c. chatroom_status(name: "yourname", status: "idle")
  3. If user says "@yourname stop" or "shutdown":
    • chatroom_broadcast(message: "leaving", category: "leaving", name: "yourname")
    • chatroom_leave(name: "yourname")
    • ONLY THEN you may exit
  4. If no shutdown command: go back to step 1
  5. NEVER EXIT THIS LOOP WITHOUT SHUTDOWN COMMAND

## The ONLY Way to Exit

- User explicitly says "@yourname stop", "shutdown", or "all agents stop"
- You see this in chatroom_check results
- Then and ONLY then: broadcast "leaving", call `chatroom_leave(name: "yourname")`, and exit

**If you are unsure whether to exit: DON'T. Keep looping.**

Read the full file on GitHub · 143 lines

Changes

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.

  1. 10d ago First seen · 143 lines · 34 tokens per session scan A 581dc6dfa2c4

Subscribe to this mod's changes

chatroom is a skill published in the GitHub repository ctb111/claude-agent-chatroom (5 stars, last pushed 7mo ago), licensed MIT. It adds 34 tokens to every session and 1,416 once invoked, about $0.0002 per session on Opus 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.

Related

Other skills, from other repositories

kb-ingest

Use when a new source document has been added to a KB's raw/ folder and needs to be filed into the wiki — read the source, write its summary page, create or update concept and entity pages, update the index and log, and lint.

hogu-dev/llmkb · 55 tokens

kb-init

Use to create a new llmkb knowledge base for a project — scaffold it with llmkb init, then interview the user briefly to tailor SCHEMA.md to the project's domain and conventions.

hogu-dev/llmkb · 44 tokens

kb-lint

Use to health-check an llmkb knowledge base — run llmkb lint and fix what it reports, then do the judgment-level checks code cannot: contradictions between pages, stale claims superseded by newer sources, and missing concept pages.

hogu-dev/llmkb · 54 tokens

kb-query

Use when answering a question from one or more llmkb knowledge bases — route via the index, search at scale, cite the pages used, and optionally file valuable new synthesis back as a page (the compounding loop).

hogu-dev/llmkb · 50 tokens

create-site

Creates a new Power Pages code site (SPA) using React, Angular, Vue, or Astro. Guides through the full process from initial concept to deployed site: requirements discovery, scaffolding, component planning, design, implementation, validation, and deployment. Use when the user wants to create, build, or scaffold a new…

microsoft/power-platform-skills · 73 tokens

add-cloud-flow

Integrates Power Automate cloud flows into a Power Pages site. Lists available flows, suggests relevant ones based on intent, identifies scenarios and web roles, creates metadata files, and generates client-side code to call flows. Handles both new flow registration and adding already-registered flows to additional…

microsoft/power-platform-skills · 91 tokens