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/sage-hq/agentcortex-mcpWrote 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/sage-hq/agentcortex-mcp/agentcortex)<a href="https://agentmods.dev/mcp/sage-hq/agentcortex-mcp/agentcortex"><img src="https://agentmods.dev/badge/mcp/sage-hq/agentcortex-mcp/agentcortex/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/sage-hq/agentcortex-mcp/agentcortex"><img src="https://agentmods.dev/badge/mcp/sage-hq/agentcortex-mcp/agentcortex.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
agentcortex 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 1mo 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
{ "agentcortex": { "command": "npx", "args": [ "-y", "agentcortex" ] } }
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.
- 1mo ago First seen · 9 lines scan A 17d251cccf16
agentcortex is an MCP server published in the GitHub repository sage-hq/agentcortex-mcp (5 stars, last pushed 1y 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-31.
Other mcp servers, from other repositories
workflows
A Model Context Protocol server that acts as an intelligent conversation state manager and development guide for LLMs, featuring comprehensive long-term memory with persistent project artifacts. Runs locally from the @codemcp/workflows npm package.
neverinfamous-memory-journal-mcp
A MCP server built for developers enabling Git based project management with project and personal… Remote server at server.smithery.ai.
sb
End-to-end agent-managed company brain. Docs, diagrams, plans, Knowledge Graph. Lean & affordable. Remote server at api.stablebaseline.io.
trail
Issue tracker and durable project memory for your coding agent, scoped to the folder you open. Runs locally from the usetrail npm package. Needs 2 environment variables to run.
connectr-mcp
Shared brain for AI coding agents - one MCP server giving Claude Code, Codex, Cursor, Kiro, Gemini CLI and Antigravity a common task board, shared memory and advisory file claims. Runs locally from the connectr-mcp npm package.
sprintra
The project brain for AI coding agents — memory, decisions, sprints, knowledge base via MCP. Runs locally from the @sprintra/mcp npm package. Needs 3 environment variables to run.