comms-import

A command for importing an old WhatsApp chat export, which is a text file containing conversation history, into a repository timeline.

In plain words
What is it for?
Reading an exported chat, matching it to an allowed conversation, and adding or merging its messages into the timeline.
Why use it?
It fills gaps in captured chat history and avoids duplicate messages when the same export is imported again.

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-import
Clone the repo
git clone --depth 1 https://github.com/DevZonayed/Mochi
Per session 31 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 300 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.00031 $0.00300
Opus 5 $0.00015 $0.00150
Sonnet 5 $0.00006 $0.00060
Haiku 4.5 $0.00003 $0.00030

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

Security

Grade A, and why

comms-import 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-import.md · 15 lines

What it actually says

Import an exported chat to fill history gaps. The user exports a chat from WhatsApp (Export chat -> without media or with media) and gives the .txt path.

  1. Confirm the target chatId (run comms_list_chats to resolve a name -> JID if the user gave a name). The chat must already be on this repo's allowlist.
  2. Call comms_import_history({provider, accountId, chatId, filePath}).
    • The importer parses each line, normalizes it to the shared message shape, and reconciles by fingerprint — re-importing the same file is idempotent (no duplicates), and live/backfill records win over imported ones for the same content.
    • WhatsApp exports are minute-resolution, so imported timestamps are less precise than live capture; that's a documented limitation.

Report counts (added vs merged). Do not print message bodies. Order is reconstructed at read time, so imported old messages slot correctly into the timeline.

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 · 15 lines · 31 tokens per session scan A a5cdebce4c77

Subscribe to this mod's changes

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