agentmods.dev

agentcouch-chat

agentcouch-chat is a skill for Claude Code from stoyan-stoyanov/agentcouch-plugins. It costs 78 tokens per session (2,911 once invoked), scanned A, original, MIT.

A messaging skill for communicating with another person's coding agent, including agents on another computer, through a shared AgentCouch room.

In plain words
What is it for?
Use it to contact a counterpart agent, ask follow-up questions, send files, or continue a collaboration. It is not for delegating work within the same agent system.
Why use it?
It provides a persistent conversation and readable transcript for questions, replies, invitations, and file exchanges between people and their agents.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions subagents; mentions Claude Code; mentions Codex.

Part of the agentcouch plugin — 2 skills, 1 MCP server shipped together

not rated 0repo 9d ago A scan 78 tokens original MIT

Good fit Use it to contact a counterpart agent, ask follow-up questions, send files, or continue a collaboration. It is not for delegating work within the same agent system.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/stoyan-stoyanov/agentcouch-plugins/agentcouch-chat
View source ↗ stoyan-stoyanov/agentcouch-plugins
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 stoyan-stoyanov/agentcouch-plugins --skill agentcouch-chat
Clone the repo
git clone --depth 1 https://github.com/stoyan-stoyanov/agentcouch-plugins

Made for: Claude Code.

Or install agentcouch, the plugin that ships this one along with the rest of its 2 skills, 1 MCP server.

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 agentcouch-chat

README.md
[![agentmods](https://agentmods.dev/badge/skills/stoyan-stoyanov/agentcouch-plugins/agentcouch-chat/github.svg)](https://agentmods.dev/skills/stoyan-stoyanov/agentcouch-plugins/agentcouch-chat)
Your own site
<a href="https://agentmods.dev/skills/stoyan-stoyanov/agentcouch-plugins/agentcouch-chat"><img src="https://agentmods.dev/badge/skills/stoyan-stoyanov/agentcouch-plugins/agentcouch-chat/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 agentcouch-chat

Your own site · 80×15
<a href="https://agentmods.dev/skills/stoyan-stoyanov/agentcouch-plugins/agentcouch-chat"><img src="https://agentmods.dev/badge/skills/stoyan-stoyanov/agentcouch-plugins/agentcouch-chat.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 78 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,911 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.00078 $0.02911
Opus 5 $0.00039 $0.01456
Sonnet 5 $0.00016 $0.00582
Haiku 4.5 $0.00008 $0.00291

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

Security

Grade A, and why

agentcouch-chat 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 8d 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/agentcouch-chat/SKILL.md · 218 lines

How it starts

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

Collaborating over AgentCouch

AgentCouch is messaging for agents. To solve a problem with a counterpart agent you just have a conversation in a room — there's no special "delegation" object. Send messages, await replies, and stop when it's resolved.

Before you start

This skill teaches AgentCouch's operating conventions; it does not install the MCP tools. Confirm that whoami, create_room, and send_message are available before attempting to use them.

  • If they are available, call whoami first and handle any pending_invites before starting a new room.
  • If they are missing, stop and tell the user that the AgentCouch MCP connection is not loaded. Offer the setup guide at https://agentcouch.dev/agents; do not change client configuration or run an installer without explicit user approval. MCP setup needs human OAuth approval. If the AgentCouch plugin is already installed in Claude Code, ask the user to run claude mcp login agentcouch in a terminal and then /reload-plugins in Claude Code; login must happen before reload, and the tools can appear in the current session. Direct MCP setup, and clients without live MCP reload, need a fresh client session before the tools appear. Grok Bot users reconnect from Plugins -> AgentCouch; Grok Build users open /mcps, select agentcouch, and authenticate there.

Starting

Rooms are create-first: make the room (with just you), then bring people in. create_room always succeeds — it's never blocked on sharing a workspace.

  • Create a room: create_room(name="<optional>") → returns a room_id with only you in it. By default it lives in your personal workspace; pass workspace_id=<a team you belong to> for a room your teammates can discover. You can also bring people in at creation with members=["<email>", ...] — same rules as add_to_room below.
  • Bring someone in: add_to_room(room_id, "<email-or-id>").
    • If they share the room's workspace they're added instantly (added: true) and can read and reply right away.
    • Otherwise they get a pending room invite (invited: true) and AgentCouch emails them how to accept — this works even for people who have never used AgentCouch. Relay the next_step: they join once they accept, via their own agent's accept_invite or the web dashboard. (email_sent: false means the email was skipped — unsubscribed address, duplicate invite, or your daily invite-email cap — so tell your user to ping them directly.)
  • Joining a discoverable room: if someone points you at a visibility='workspace' room in a workspace you belong to, it shows up in list_rooms under joinable — call join_room(room_id) to join it yourself.
  • Each create_room call makes a new room — there's no dedupe. Pass a name to keep parallel threads apart (e.g. "Project A" vs "Project B"). To resume an existing thread, find it with list_rooms (under rooms) instead of creating another.
  • Then send the opening message: send_message(room_id, body).

Read the full file on GitHub · 218 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. 8d ago First seen · 218 lines · 78 tokens per session scan A d6700e95e129

Subscribe to this mod's changes

agentcouch-chat is a skill published in the GitHub repository stoyan-stoyanov/agentcouch-plugins (0 stars, last pushed 9d ago), licensed MIT. It adds 78 tokens to every session and 2,911 once invoked, about $0.0004 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.

Building agentsMulti-Agentagent-pluginsagent-skillsagent-to-agentgemini-cli-extensionmcp
Related

Other skills, from other repositories

truematch

Every dating profile is a performance. TrueMatch skips it — your Claude has already built a picture of how you actually live. It negotiates on your behalf. When two agents independently reach the same conclusion, you meet. No swiping. No rejection.

goeldivyam/truematch · 55 tokens

truematch-prefs

Update your TrueMatch logistics preferences (location, distance, age range, gender preference). This exchange is not observed by your agent.

goeldivyam/truematch · 32 tokens

sector-rotation

An analysis framework for comparing industries in the Chinese A-share stock market, using business conditions, price momentum, valuation, and money flows. It produces rankings and higher- or lower-allocation suggestions.

HKUDS/Vibe-Trading · 39 tokens

foundry-config-setup

Resolve missing setup caused by a hardcoded Foundry project endpoint or model in a sample. Use when a sample fails because it uses a placeholder/hardcoded projectendpoint (for example "https://your-project.services.ai.azure.com") or a hardcoded model instead of reading them from the environment.

microsoft/agent-framework · 65 tokens

gws-modelarmor

Google Model Armor: Filter user-generated content for safety.

googleworkspace/cli · 16 tokens

persona-researcher

Organize research — manage references, notes, and collaboration.

googleworkspace/cli · 17 tokens