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/mcp/beevibe-ai/beevibe-cto/claude-code-skill-adr)<a href="https://agentmods.dev/mcp/beevibe-ai/beevibe-cto/claude-code-skill-adr"><img src="https://agentmods.dev/badge/mcp/beevibe-ai/beevibe-cto/claude-code-skill-adr.svg" alt="Measured on agentmods" height="20"></a>Grade 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 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
{
"adr": {
"command": "adr-mcp",
"env": {
"ADR_OPENAI_API_KEY": "${ADR_OPENAI_API_KEY}",
"OPENAI_API_KEY": "${OPENAI_API_KEY}",
"BRAVE_SEARCH_API_KEY": "${BRAVE_SEARCH_API_KEY}",
"TAVILY_API_KEY": "${TAVILY_API_KEY}",
"SERPER_API_KEY": "${SERPER_API_KEY}",
"SEARXNG_URL": "${SEARXNG_URL}",
"ADR_MODEL": "${ADR_MODEL}",
"GITHUB_TOKEN": "${GITHUB_TOKEN}"
}
}
}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 · 15 lines scan A 18b26aee41ed
adr is an MCP server 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: an MCP server costs its tool schemas, not its config file. 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 mcp servers, from other repositories
citeguard-cli
Check a bibliography for retracted papers -- retractions, corrections, and expressions of concern via Crossref (including Retraction Watch records). CLI, Python library, MCP server, GitHub Action. Runs locally from the citeguard-cli Python package.
tokens-studio-mcp
MCP server "tokens-studio-mcp" as configured in Blyawon/tokensStudioMCP. Runs locally from the tokens-studio-mcp npm package.
rewynd
MCP server "rewynd" as configured in SrinjoyDev/rewynd. Launched with rewynd mcp.
tracer
MCP server "tracer" as configured in aiquilibria/contAIned. Runs contained.tracer_mcp with python3.
cold-run
Run every skill in your agent setup twice — once with it, once against an agent that cannot see it — and find out which ones change nothing. Runs locally from the cold-run npm package.
golden-egg
MCP server "golden-egg" as configured in joehwang/goldenegg-tw-holdings-cli. Runs locally from the golden-egg Python package.