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.
git clone --depth 1 https://github.com/Agenxy/dibsWrote 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/agenxy/dibs/claude-code)<a href="https://agentmods.dev/plugins/agenxy/dibs/claude-code"><img src="https://agentmods.dev/badge/plugins/agenxy/dibs/claude-code/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/plugins/agenxy/dibs/claude-code"><img src="https://agentmods.dev/badge/plugins/agenxy/dibs/claude-code.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade 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 9d 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.
The source is not reproduced here
Licensed GPL-3.0
The repository is licensed GPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
What it installs
The manifest is a name and a version. 1 skill, 2 hooks, 1 MCP server travel with it, and installing the plugin installs all of them — 68 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 9d ago Changed b47c2d908f5c
- 10d ago Changed 72e03fd023e9
- 11d ago Changed f52d37c7c0a0
- 13d ago Changed 07588513ac1d
- 24d ago Changed 97c274c55222
- 1mo ago Changed bc9f75e779a0
- 1mo ago First seen · 18 lines scan A e51f889fe7a4
dibs is a plugin published in the GitHub repository Agenxy/dibs (2 stars, last pushed yesterday), licensed GPL-3.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.
murmur
Read and send Murmur messages through MCP, with explicit inbox and terminal status helpers.
sema
Content-addressed vocabulary protocol — shared meaning for AI agents.
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.
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.