rooms-test

rooms-test is a command for Claude Code from dork-labs/dorkos. It costs 58 tokens per session (13,523 once invoked), scanned E, original, MIT.

A live browser test for DorkOS rooms, where people and multiple agents share a channel. It checks the visible behavior against the room API and the SQLite database, which stores the room data.

In plain words
What is it for?
Use it after changing room services, message dispatch, message collection, notices, reactions, threads, or the room event stream.
Why use it?
It finds problems that appear only when several participants interact in one room. The resulting report links observed behavior to the documented capability rules.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: names the AskUserQuestion tool.

Part of the flow plugin — 43 skills, 45 commands, 5 agents, 4 hooks shipped together

Good fit Use it after changing room services, message dispatch, message collection, notices, reactions, threads, or the room event stream.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/dork-labs/dorkos/rooms-test
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.

Clone the repo
git clone --depth 1 https://github.com/dork-labs/dorkos

Made for: Claude Code.

Or install flow, the plugin that ships this one along with the rest of its 43 skills, 45 commands, 5 agents, 4 hooks.

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 rooms-test

README.md
[![agentmods](https://agentmods.dev/badge/commands/dork-labs/dorkos/rooms-test/github.svg)](https://agentmods.dev/commands/dork-labs/dorkos/rooms-test)
Your own site
<a href="https://agentmods.dev/commands/dork-labs/dorkos/rooms-test"><img src="https://agentmods.dev/badge/commands/dork-labs/dorkos/rooms-test/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 rooms-test

Your own site · 80×15
<a href="https://agentmods.dev/commands/dork-labs/dorkos/rooms-test"><img src="https://agentmods.dev/badge/commands/dork-labs/dorkos/rooms-test.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 58 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 13,523 The whole file, excluding the scripts and references it only reads on demand.
Security scan E 3 findings. A grade says what 26 rules found in the file — not that it is safe. ✓ AI security review Sonnet 5 · 7 Sept 2026 📄 Read the review
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.00058 $0.13523
Opus 5.5 $0.00023 $0.05409
Sonnet 5.5 $0.00012 $0.02705
Haiku 4.5 $0.00006 $0.01352

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

Security

Grade E, and why

rooms-test scanned grade E with 3 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 13d 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.

Downloads and executes remote codehighSupply chain

curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.

curl -s "http://localhost:$API_PORT/api/mesh/agents" | python3 -c "

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

dotenv -- sh -c 'rm -rf /tmp/dorkos-test-mode-4243 && turbo run build --filter=@dorkos/server && pnpm --filter @dorkos/server exec tsx src/index.ts'

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -sf -X PATCH http://localhost:4248/api/config -H 'content-type: application/json' \
.claude/commands/chat/rooms-test.md · 626 lines

How it starts

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

Self-test the parts of DorkOS that only exist when more than one participant shares a room: a channel with two agents and you, driven through a message burst, a mid-turn arrival, a halt, a reaction, a thread, a document on the room's shared canvas, and the three-way rule that keeps you in any room two agents share. The command drives the browser, cross-checks the room API and the SQLite rows underneath it, and writes an evidence-based report.

It is the rooms sibling of /chat:self-test (one session, in depth) and /chat:session-switch-test (two sessions, switching). Use it whenever you touch RoomService, the trigger dispatcher, the collector, room notices, reactions, threads, the room canvas, or the room event stream.

Every check below cites the capability row it verifies in contributing/capabilities/chat.md — a run of this command is a report against that contract, not a vibe check.


Argument Parsing

Parse $ARGUMENTS:

  1. URL — any arg starting with http. Default http://localhost:6241/channels (live) or http://localhost:4248/channels (sandbox — see Phase 1).
  2. mode:sandbox|live — which stack the run drives (contributing/capabilities/chat.md §11).
    • mode:sandbox — the test-mode runtime: throwaway data dir, deterministic, no model spend. Room turns really happen (the chromium-team-room e2e project proves an agent answers under this runtime), so every mechanical check below is reachable. What is not reachable is every check whose verdict is a judgment about what the agent chose to say — those are marked N/A (sandbox), never PASS.
    • mode:live — the dev stack with a real runtime. Two agents answer per burst, so budget accordingly.
    • If the invocation does not state a mode, ASK the user before spending anything (AskUserQuestion, offering both with their costs). Never assume live.
  3. perm:<mode> — permission mode for the agents' room-bound sessions. Default acceptEdits, which is the right default here and not a shortcut: a pending tool approval stalls a room turn, and a stalled turn makes checks 1–4 unreadable (you cannot tell "the agent folded three messages into one reply" from "the agent never got past a gate"). Use default only when the run is deliberately about approvals in rooms, and expect the downstream checks to come back BLOCKED.
  4. model:<id> — default claude-haiku-4-5. Ignored under mode:sandbox.
  5. agents:a,b — the two agents to seat in the channel. Default: the first two agents the create dialog's agent search offers. Pick two whose display names are not prefixes of one another — half the assertions here locate an entry by its author's rendered name, and bo inside bobby will find the wrong row.

Store as TEST_URL, MODE, PERM_MODE, MODEL, AGENT_A, AGENT_B.

Read the full file on GitHub · 626 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. 13d ago Changed · -2 lines a74969bcf31e
  2. 18d ago Changed 217d449753b1
  3. 20d ago Changed bae7be8bd63c
  4. 1mo ago Changed · +94 lines · +4 tokens per session 5ebcb183a68b
  5. 1mo ago First seen · 534 lines · 54 tokens per session scan E 0a36fe7dcd93

Subscribe to this mod's changes

rooms-test is a command published in the GitHub repository dork-labs/dorkos (12 stars, last pushed today), licensed MIT. It adds 58 tokens to every session and 13,523 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it E with 3 findings (downloads and executes remote code, recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.