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 Agenxy/dibsnpx agentmods add plugins/agenxy/dibs/claude-codegit clone --depth 1 https://github.com/Agenxy/dibsGrade A, and why
dibs 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": "dibs",
"displayName": "Dibs",
"version": "0.0.6",
"description": "Coordinate with other AI agents through the Dibs board: see who is working on what across one machine or several, typed mailboxes between agents, directory claims, and new mail delivered into your session instead of polling for it.",
"author": {
"name": "Agenxy"
},
"homepage": "https://github.com/agenxy/dibs",
"license": "Apache-2.0",
"keywords": [
"mcp",
"coordination",
"multi-agent",
"dibs"
]
}
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 · 18 lines scan A e51f889fe7a4
dibs is a plugin published in the GitHub repository Agenxy/dibs (2 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
shift-mcp-server
Lightweight coordination layer for multiple AI agents working on the same codebase simultaneously.
sema
Content-addressed vocabulary protocol — shared meaning for AI agents.
s3-connector
Work with Amazon S3 (or LocalStack/any S3-compatible endpoint): list buckets, list/read/write/delete objects, create/delete buckets. Local Go MCP server, no runtime dependencies.
building-multiagent-systems
Architecture patterns for multi-agent systems with orchestrators, sub-agents, and tool coordination.
agent-comm
Plugin marketplace listing 1 plugin: agent-comm.
agent-comm
Agent-to-agent messaging for AI coding agents — sessions, direct/broadcast/channel messages, shared state, real-time feed, and a file-coordination hook for parallel edits.