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 n24q02m/claude-pluginsnpx agentmods add plugins/n24q02m/claude-plugins/agent-chat-plugingit clone --depth 1 https://github.com/n24q02m/claude-pluginsGrade A, and why
agent-chat-plugin 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.
What it actually says
{
"name": "agent-chat-plugin",
"description": "Peer AI agents coordinate through markdown messages in shared channel folders — group chat / blackboard, no orchestrator, autonomous zero-token waiting, cross-platform.",
"version": "0.4.0",
"author": {
"name": "n24q02m",
"url": "https://github.com/n24q02m"
},
"homepage": "https://github.com/n24q02m/agent-chat-plugin",
"userConfig": {
"AGENT_CHAT_NAME": {
"type": "string",
"title": "Agent identity",
"description": "This session's name in the chat (e.g. claude-1). Required for the inbox hook.",
"required": false
},
"AGENT_CHAT_ROOT": {
"type": "string",
"title": "Chat root directory",
"description": "Where channels live. Default: ~/agent-chat",
"required": false
},
"AGENT_CHAT_CHANNELS": {
"type": "string",
"title": "Channels to watch",
"description": "Comma-separated channels checked at session start. Empty = all.",
"required": false
}
},
"mcpServers": {}
}
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 · 32 lines scan A 01561512684f
agent-chat-plugin is a plugin published in the GitHub repository n24q02m/claude-plugins (3 stars, last pushed 2d ago), licensed Apache-2.0. 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
sodam-persona
Plugin marketplace listing 1 plugin: sodam-persona.
sodam-persona
바이브코딩 AI 개발 파트너 페르소나 v5 — 항상켜짐 코어(hook) + 조건부 15관점/도메인(skills).
review
PR review, interactive git diff annotation review, and writing style guide.
ballast
Builds up to a goal in a field you have no expertise in — learns the foundations it needs and keeps every solved path for the next goal.
makoto
Plugin marketplace listing 1 plugin: makoto.
dev-tooling
Three MCP servers for PHP and JavaScript operations plus an optional PHP language server. PHP (php-tooling): PHPStan, ECS, Rector, PHPUnit, PHPUnit coverage gap analysis, Symfony Console. Administration (js-admin-tooling): ESLint, Stylelint, Prettier, Jest, TypeScript, Vite builds. Storefront (js-storefront-tooling)…