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/infimium-ai/infimium-agentWrote 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/infimium-ai/infimium-agent/infimium)<a href="https://agentmods.dev/mcp/infimium-ai/infimium-agent/infimium"><img src="https://agentmods.dev/badge/mcp/infimium-ai/infimium-agent/infimium/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/infimium-ai/infimium-agent/infimium"><img src="https://agentmods.dev/badge/mcp/infimium-ai/infimium-agent/infimium.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
infimium 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 9d 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
{
"infimium": {
"command": "npx",
"args": [
"-y",
"infimium",
"serve"
]
}
}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.
- 9d ago First seen · 10 lines scan A 009269fb6172
infimium is an MCP server published in the GitHub repository infimium-ai/infimium-agent (22 stars, last pushed 23d ago), licensed MIT. 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
opencontext
A Model Context Protocol server for persistent project-specific AI agent context. Runs locally from the opencontext-mcp npm package.
contextgit
MCP server "contextgit" as configured in RT123-new/contextgit-mcp. Runs locally from the contextgit-mcp Python package. Needs 1 environment variable 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…
hypermnesia-mcp
Scientifically-grounded memory system based on computational neuroscience research. Runs locally from the hypermnesia-mcp Python package.
rag-rat
CLI and MCP entrypoint for indexing repositories into local source, graph, history, and memory evidence. Runs locally from the @rag-rat/bin npm package.
pmll-memory-mcp
PMLL Memory MCP Server v2 — persistent memory logic loop with short-term KV cache (peek pattern), Q-promise deduplication, Context+ long-term semantic memory graph, and solution engine. Four-way benchmarked: Combined Context+ + PMLL/peek delivers 36ms (TS) / 78ms (PY) total — fastest configuration. 15 tools…