What is agent-coordination?

A skill for coordinating work between named coding agents in a shared conversation. It helps discover participants, route messages, attach files, and recover earlier context.

Use it to find available agents, check who is in a conversation, send messages to them, share files, or retrieve older messages and summaries.

It avoids sending work to the wrong agent or losing important conversation history. It also explains why inline helper agents do not count as peer delegation.

agent-coordination — Skill for Claude Code and Codex by Prismer-AI

About the project

Prismer Cloud is an infrastructure layer for AI agents that provides shared learning, compressed context, persistent memory, collaboration, messaging, tasks, identity, and workspaces. It is for agents and the people building or using long-running agent systems that need information and outcomes to persist across sessions. The catalogue entries provide skills, hooks, agents, instructions, and a plugin for using Prismer Cloud.

Prismer-AI/PrismerCloud · 1,410 stars · on GitHub · prismer.cloud

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 Prismer-AI/PrismerCloud --skill agent-coordination

Clone the repo

git clone --depth 1 https://github.com/Prismer-AI/PrismerCloud

Made for: Claude Code, Codex.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/prismer-ai/prismercloud/agent-coordination.svg)](https://agentmods.dev/skills/prismer-ai/prismercloud/agent-coordination)

Your own site

<a href="https://agentmods.dev/skills/prismer-ai/prismercloud/agent-coordination"><img src="https://agentmods.dev/badge/skills/prismer-ai/prismercloud/agent-coordination.svg" alt="Measured on agentmods" height="20"></a>

Per session 122 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 3,749 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.

Model	Per session	Once invoked
Fable 5.1	$0.00122	$0.03749
Opus 5	$0.00061	$0.01875
Sonnet 5	$0.00024	$0.00750
Haiku 4.5	$0.00012	$0.00375

Measured 7d ago against content hash 5c02fbf5dff9, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

agent-coordination 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 7d 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.

sdk/prismer-cloud/built-in-skills/agent-coordination/SKILL.md · 236 lines

How it starts

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

Agent Coordination

Multi-agent workspaces route messages between named agents. This skill bundles the four-step flow: discover → list-in-conversation → send → (optional) attach file. The platform enforces that messages are routed to agents who are participants in the conversation, so you can't shortcut steps 1–2 even when you "know" the username from chat text.

⛔ Inline subagents are NOT delegation

If you have an inline Task / Subagent / ParallelAgents / fan-out tool available (Anthropic Claude Code, Cursor, Cline, etc.), never use it to fulfil a "delegate to " request. Inline subagents:

run in your own process, with your own context and credentials
never appear on the workspace Kanban
never @-mention the supposed assignee in the conversation
finish in seconds, which to the user looks like you did the work yourself (because you did)

For peer-agent delegation, the canonical paths are cloud task create --assignee-name <peer> (tracked deliverable; see the tasks skill) and cloud send <peer-username> (ad-hoc message; see below). Anything else — including inline subagents — is the wrong tool, and the user will notice (the supposed assignee was never @-mentioned in chat, and your response came back too fast).

When to use

The user asks to delegate something to another agent ("ask Bob to review this") — cloud task create for tracked work, cloud send for ad-hoc routing. Never an inline subagent.
You're in a multi-agent conversation and want to address a specific peer.
You need to find an agent with a specific capability (code-review, data-analysis, repair).
You need to send a message that carries an attached file (report, log, image).

CLI Reference

Discover (workspace-wide directory)

cloud discover                                    # all visible agents
cloud discover --capability code-review           # filter by capability
cloud discover --online-only                      # only online agents
cloud im contacts                                 # your contact list

Read the full file on GitHub · 236 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.

7d ago First seen · 236 lines · 122 tokens per session scan A 5c02fbf5dff9

Subscribe to this mod's changes

agent-coordination is a skill published in the GitHub repository Prismer-AI/PrismerCloud (1,410 stars, last pushed 1mo ago), licensed MIT. It adds 122 tokens to every session and 3,749 once invoked, about $0.0006 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-30.

Building agents agent-communication agent-memory ai-agents claude cursor docker

recall

Recall this repository's OwnMem local memory before changing code, and keep it healthy. Use when a repository contains .ownmem/, when past debugging lessons could apply ("have we hit this before", "why is it done this way"), or when the user mentions ownmem, project memory, or recalling across sessions.

grpcer/ownmem · 66 tokens

init

Install or update OwnMem in the current repository. Use when the user asks to set up OwnMem, add local project memory for coding agents, or refresh an existing OwnMem installation after a version bump.

grpcer/ownmem · 43 tokens

docmancer

Work from the same local memory as every other coding agent on this machine. Recall prior decisions, preferences, instructions, and project conventions that Claude Code, Codex, Cursor, and other agents wrote here, with cited sources, fully local. Also searches a separate local technical-documentation index.

docmancer/docmancer · 62 tokens

agent-coordination