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/Kyrzin/kybaseWrote 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/kyrzin/kybase/kybase-mcp-kybase)<a href="https://agentmods.dev/mcp/kyrzin/kybase/kybase-mcp-kybase"><img src="https://agentmods.dev/badge/mcp/kyrzin/kybase/kybase-mcp-kybase/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/mcp/kyrzin/kybase/kybase-mcp-kybase"><img src="https://agentmods.dev/badge/mcp/kyrzin/kybase/kybase-mcp-kybase.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket warn
Grade A, and why
kybase 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 7d 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 AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 7d ago First seen · 18 lines scan A 9f36761c79cb
kybase is an MCP server published in the GitHub repository Kyrzin/kybase (5 stars, last pushed 8d ago), licensed AGPL-3.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-10-03.
Other mcp servers, from other repositories
tacitus-mcp-server
Long-term memory for AI agents: local-first PKM with provenance and hybrid search. Runs locally from the @dashiro/tacitus-mcp-server npm package.
auto-knowledge-base
MCP server "auto-knowledge-base" as configured in guyeyouhun/auto-knowledge-base. Runs locally from the auto-knowledge-base npm package.
agentbase
Shared knowledge base for AI agents. Semantic search across agents, no setup required — just a URL. Remote server at mcp.agentbase.tools.
prism-coder
Session memory for coding agents: local-first recall, drift detection, on-device inference. Runs locally from the prism-mcp-server npm package. Needs 8 environment variables to run.
prism-mcp
Persistent session memory for AI coding agents that never leaves your machine — including the on-device model that reasons over it. Restores your prior decisions, open TODOs, and changed files across sessions; adds associative recall of related past work. Runs locally from the prism-mcp-server npm package. Needs 1…
ai-memory
MCP server "ai-memory" as configured in alphaonedev/ai-memory-mcp. Runs in Docker (ghcr.io/alphaonedev/ai-memory:0.5.1). Needs 1 environment variable to run.