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/beevibe-ai/beevibe-ctoWrote 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/beevibe-ai/beevibe-cto/marketplace)<a href="https://agentmods.dev/plugins/beevibe-ai/beevibe-cto/marketplace"><img src="https://agentmods.dev/badge/plugins/beevibe-ai/beevibe-cto/marketplace.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
beevibe 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 8d 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
{
"$schema": "https://anthropic.com/claude-code/marketplace.schema.json",
"name": "beevibe",
"description": "Beevibe Claude Code plugins. Currently: Architecture Deep Research (live, evidence-only research for system-design decisions).",
"owner": {
"name": "Beevibe",
"email": "[email protected]",
"url": "https://github.com/beevibe-ai"
},
"plugins": [
{
"name": "adr",
"description": "Architecture Deep Research — scan a repo, draft a PRD, run live deep research, get a cited handoff. Use when picking a topology, retrieval architecture, event bus, storage engine, auth pattern, or any system-design decision before code lands.",
"author": {
"name": "Beevibe"
},
"category": "agent-orchestration",
"source": {
"source": "git-subdir",
"url": "https://github.com/beevibe-ai/beevibe-cto.git",
"path": "plugin",
"ref": "main"
},
"homepage": "https://github.com/beevibe-ai/beevibe-cto"
}
]
}
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 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.
- 8d ago First seen · 28 lines scan A f3ff25b93e86
beevibe marketplace is a plugin published in the GitHub repository beevibe-ai/beevibe-cto (105 stars, last pushed 2mo 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-30.
Other plugins, from other repositories
agent-deck
Complete guide for managing AI coding agent sessions via agent-deck CLI - session lifecycle, MCP management, groups, profiles, and automation.
jk
GitHub CLI-style interface for Jenkins controllers - create multibranch jobs, inspect config.xml, and manage runs, logs, artifacts, credentials, nodes, and queues.
b2c-cli
B2C CLI Skills for Salesforce Commerce Cloud development.
rudder
Maintain a device-local spec from coding-session intent, then generate focused unit tests with your existing coding agent.
tree-ring-memory
Local-first memory lifecycle, project bootstrap, and receipt-backed harness guidance for Claude Code using Tree Ring Memory v0.15+.
humanizer
Rewrite AI-sounding text so it reads naturally without changing what it says.