start

A command that starts a shared online backchannel room and prints a link that others can use to join it.

In plain words
What is it for?
Use it when you need to create a new shared backchannel and share its joining link with other people.
Why use it?
It provides a room for private coordination alongside the main work, without requiring you to set one up manually.

Command

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.

agentmods
npx agentmods add commands/j-ronk/backchannel/start
Clone the repo
git clone --depth 1 https://github.com/j-ronk/backchannel
Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 216 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00013 $0.00216
Opus 5 $0.00006 $0.00108
Sonnet 5 $0.00003 $0.00043
Haiku 4.5 $0.00001 $0.00022

Measured yesterday against content hash a3505b606f75, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

start 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 yesterday.

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.

client/commands/start.md · 14 lines

What it actually says

The backchannel CLI output below contains the room link(s). You MUST print that output to the user verbatim and in full, including every complete link character-for-character (the whole https://…/r/…#k=… string, fragment included). The links are the entire purpose of this command — reproducing them is mandatory and non-negotiable.

  • Do NOT summarize, paraphrase, shorten, describe, or omit the links.
  • Do NOT replace a link with a sentence about it.
  • It is fine to add a one-line note after, but the full links must appear first.
  • A display name is REQUIRED. If it is missing, the CLI prints a usage error — relay that verbatim instead.

!"${CLAUDE_PLUGIN_ROOT}/bin/backchannel" start --name "$ARGUMENTS"

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. yesterday First seen · 14 lines · 13 tokens per session scan A a3505b606f75

Subscribe to this mod's changes

start is a command published in the GitHub repository j-ronk/backchannel (1 stars, last pushed 1mo ago), licensed MIT. It adds 13 tokens to every session and 216 once invoked, about $0.0001 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.