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.
/plugin marketplace add KARPED1EM/CC-Group-Chatnpx agentmods add plugins/karped1em/cc-group-chat/marketplacegit clone --depth 1 https://github.com/KARPED1EM/CC-Group-ChatWrote 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.
[](https://agentmods.dev/plugins/karped1em/cc-group-chat/marketplace)<a href="https://agentmods.dev/plugins/karped1em/cc-group-chat/marketplace"><img src="https://agentmods.dev/badge/plugins/karped1em/cc-group-chat/marketplace.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
cc-group-chat-marketplace 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 5d 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.
What it actually says
{
"name": "cc-group-chat-marketplace",
"owner": {
"name": "KARPED1EM",
"email": "[email protected]"
},
"plugins": [
{
"name": "cc-group-chat",
"source": {
"source": "github",
"repo": "KARPED1EM/CC-Group-Chat"
},
"description": "Cross-window group chat for Claude Code"
}
]
}
The plugins it lists here
This marketplace lists 1 plugin kept in the same repository. Each has its own page, its own measurements and its own install command.
What ships with it
1 file beside marketplace.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 18 lines scan A 7f9c62750e7f
cc-group-chat-marketplace is a plugin published in the GitHub repository KARPED1EM/CC-Group-Chat (4 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.
Other plugins, from other repositories
dashi-channel
Telegram channel plugin for Claude Code: personal DM bridge + public multichat, permission relay, confirm-panel keys, context HUD with a single pinned status card, rich messages (Bot API 10.1), Guest Mode, voice transcription, terminal mirror, secret redaction.
mcp-recall
Context compression and persistent retrieval for Claude Code.
captain-memo
Cross-AI local memory layer (Claude Code, Codex, Gemini, Cursor) — hybrid search, three summarizer providers, self-hosted embedder. Replaces claude-mem.
msteams
Microsoft Teams channel for Claude Code: DMs and mention-gated channel messages over the Microsoft Agents SDK, with tenant/sender allowlists and pairing. Manage access via /msteams:access.
plugin-claude-npm-bun-guard
Modèle de garde-fou d'installation npm/bun : refuse les paquets malveillants connus (arbre transitif inclus) et met en quarantaine les versions publiées depuis moins de 3 jours.
cassandra
Remembers the tool calls that already failed, and says so before your agent runs one again unchanged.