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 beevibe-ai/beevibe-ctonpx agentmods add plugins/beevibe-ai/beevibe-cto/plugingit clone --depth 1 https://github.com/beevibe-ai/beevibe-ctoGrade A, and why
adr 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 2d 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": "adr",
"version": "0.2.0",
"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",
"url": "https://github.com/beevibe-ai"
},
"repository": "https://github.com/beevibe-ai/beevibe-cto",
"license": "Apache-2.0",
"homepage": "https://github.com/beevibe-ai/beevibe-cto",
"keywords": [
"architecture",
"deep-research",
"system-design",
"adr",
"decision-records",
"agent",
"mcp",
"beevibe"
],
"commands": [
"./commands/decide.md",
"./commands/discover.md",
"./commands/doctor.md",
"./commands/guard.md",
"./commands/principles.md",
"./commands/review.md"
]
}
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.
- 2d ago First seen · 31 lines scan A a7aa08fa8eac
adr 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
autosearch
Self-evolving deep research. Gets smarter every time you use it. Searches across channels, synthesizes cited reports, and learns which queries and platforms work best.
antigravity
Antigravity plugin for Claude Code with TRAID Design System: 5 canonical HTML templates (traid-dark, traid-light, stripe-press, notion-docs, magazine) for branded report generation from markdown. Plus audio & video transcription (/agy:transcribe, /agy:media), a local NotebookLM (/agy:notebook — sweep a folder of…
autosearch
Plugin marketplace listing 1 plugin: autosearch.
lit-review-marketplace
Plugin marketplace listing 1 plugin: lit-review-agent-tools.
lit-review-agent-tools
Recommend AND run open-source AI literature-review tools — a curated 70+ catalog plus a launcher that installs & runs MinerU, PaperQA2, ASReview, GPT Researcher, STORM, and arXiv/Zotero MCP servers.
giasip-skills
GiaSip skills for evidence-gated research orchestration and multi-model dispatch.