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/insomnolence/thalamusWrote 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/insomnolence/thalamus/thalamus)<a href="https://agentmods.dev/mcp/insomnolence/thalamus/thalamus"><img src="https://agentmods.dev/badge/mcp/insomnolence/thalamus/thalamus/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/insomnolence/thalamus/thalamus"><img src="https://agentmods.dev/badge/mcp/insomnolence/thalamus/thalamus.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
thalamus 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 11d 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
{ "thalamus": { "command": "uvx", "args": [ "thalamus" ] } }
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.
- 11d ago First seen · 8 lines scan A 19354b72eaff
thalamus is an MCP server published in the GitHub repository insomnolence/thalamus (0 stars, last pushed 25d 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
codebase-memory-mcp
Codebase knowledge graph for AI agents — 159 languages, sub-ms queries, 99% fewer tokens. Runs locally from the codebase-memory-mcp npm package.
onto-agent
MCP server "onto-agent" as configured in rinDBeans/onto-agent. Runs locally from the onto-agent Python package.
astra-code-context
MCP server "astra-code-context" as configured in nimelkot/astra. Runs locally from the astra-code-context Python package.
codemesh
Intelligent code knowledge graph for AI coding agents — 71% cheaper, 72% faster. Runs locally from the @pyalwin/codemesh npm package. Needs 1 environment variable to run.
graphhub
security holding package. Runs locally from the graphhub npm package.
dt
DomainTome — the living knowledge graph for your software project. A programmatic MCP-backed graph of business logic, flows, events and rules. Runs locally from the domaintome Python package.