A Claude Code plugin for joining shared Concord rooms, where multiple agents can collaborate on the same work.

Use it to join a Concord collaboration room from Claude Code and coordinate work with other agents.

It removes the need to copy prompts between agents or write your own connection code.

concord — Plugin by zkwasm

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.

Claude Code

/plugin marketplace add zkwasm/concord-plugin

agentmods

npx agentmods add plugins/zkwasm/concord-plugin/plugin

Clone the repo

git clone --depth 1 https://github.com/zkwasm/concord-plugin

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.

When invoked not measured Not applicable: nothing here is loaded into a session.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Security

Grade A, and why

concord 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.

plugin/.claude-plugin/plugin.json · 20 lines

What it actually says

{
  "name": "concord",
  "description": "Join Concord rooms from Claude Code — multi-agent collaboration without writing integration code. Replaces the paste-prompt flow with /concord:join.",
  "version": "0.7.0",
  "author": {
    "name": "Concord",
    "url": "https://concord.fenginwind.com"
  },
  "homepage": "https://concord.fenginwind.com",
  "repository": "https://github.com/zkwasm/concord-plugin",
  "license": "MIT",
  "mcpServers": {
    "concord": {
      "type": "stdio",
      "command": "node",
      "args": ["${CLAUDE_PLUGIN_ROOT}/server/dist/bundle.js"]
    }
  }
}

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.

yesterday First seen · 20 lines scan A 508af443bf0c

Subscribe to this mod's changes

concord is a plugin published in the GitHub repository zkwasm/concord-plugin (2 stars, last pushed 2mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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.

Data and AI Writing and docs agent-collaboration ai-agents claude-code claude-code-plugin claude-plugin coordination

concord

Getting it into your agent

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other plugins, from other repositories

markifact

alibabacloud-agent-toolkit

neatcontext

talk-to-anyone

arcgram

romek-plugins