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/CPT-Rabbit/CPT-KonsiliumWrote 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/cpt-rabbit/cpt-konsilium/konsilium)<a href="https://agentmods.dev/mcp/cpt-rabbit/cpt-konsilium/konsilium"><img src="https://agentmods.dev/badge/mcp/cpt-rabbit/cpt-konsilium/konsilium/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/cpt-rabbit/cpt-konsilium/konsilium"><img src="https://agentmods.dev/badge/mcp/cpt-rabbit/cpt-konsilium/konsilium.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
konsilium 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
{ "konsilium": { "command": "uvx", "args": [ "konsilium" ] } }
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 · 8 lines scan A 686e26a25c72
konsilium is an MCP server published in the GitHub repository CPT-Rabbit/CPT-Konsilium (0 stars, last pushed 1mo 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-31.
Other mcp servers, from other repositories
memos
Universal, local-first, persistent memory layer for AI agents, LLM apps, and chatbots. Runs locally from the @mem-os/sdk npm package.
greedy-token
MCP server "greedy-token" as configured in svasenkov/greedy-token. Launched with greedy-token-mcp. Needs 1 environment variable to run.
chimeraforge
LLM deployment optimizer (performance, cost, and safety) — backed by 204,000 real measurements on consumer GPUs. Runs locally from the chimeraforge Python package.
medical-codes-mcp-server
Offline US medical code lookup and crosswalk — ICD-10-CM/PCS, HCPCS Level II, RxNorm. Keyless. Runs locally from the @cyanheads/medical-codes-mcp-server npm package. Needs 3 environment variables to run.
forkmind
Branchable LLM history DAG + encrypted context capsules agents can save, restore, and crypto-shred. Runs locally from the forkmind npm package.
rule-drift
Test whether AI agents retain critical instructions as conversations grow. Runs locally from the rule-drift npm package.