comms-status

A command that reports the health of this repository's synchronized communication channels without showing message contents.

In plain words
What is it for?
Checking account connection status, listing approved chats, and showing message counts and the newest activity time.
Why use it?
It helps identify disconnected accounts, unavailable logins, and stale synchronization without exposing chat history.

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/devzonayed/mochi/comms-status
Clone the repo
git clone --depth 1 https://github.com/DevZonayed/Mochi
Per session 16 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 221 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.00016 $0.00221
Opus 5 $0.00008 $0.00111
Sonnet 5 $0.00003 $0.00044
Haiku 4.5 $0.00002 $0.00022

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

Security

Grade A, and why

comms-status 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.

plugins/continuum/commands/comms-status.md · 13 lines

What it actually says

Report the comms sync health for this repo. Provider defaults to whatsapp; if accountId is omitted and only one account is linked, use it — otherwise ask which.

  1. Call comms_account_status({provider, accountId}) and report connected / needs_login / logged_out.
  2. Call comms_list_chats({provider, accountId}) to show the allowlisted chats and their latest activity.

Present a compact status table: account, link status, chats synced, newest message time per chat. If an account shows needs_login or logged_out, tell the user to run /mochi:comms-setup. Do not print message bodies — this is a health summary only.

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 · 13 lines · 0 tokens per session scan A 9a2a01583f12

Subscribe to this mod's changes

comms-status is a command published in the GitHub repository DevZonayed/Mochi (3 stars, last pushed 15d ago), licensed MIT. It adds 16 tokens to every session and 221 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.