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/cdeust/CortexWrote 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/plugins/cdeust/cortex/marketplace)<a href="https://agentmods.dev/plugins/cdeust/cortex/marketplace"><img src="https://agentmods.dev/badge/plugins/cdeust/cortex/marketplace/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/plugins/cdeust/cortex/marketplace"><img src="https://agentmods.dev/badge/plugins/cdeust/cortex/marketplace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
cortex-plugins marketplace 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 22d 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.
How it starts
The opening of the file, as written. The whole thing — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
{
"name": "cortex-plugins",
"owner": {
"name": "Clement Deust",
"email": "[email protected]"
},
"metadata": {
"description": "The Cortex family of Claude Code plugins: home of hypermnesia-mcp (the persistent-memory server formerly named cortex, renamed in v4.15.0 over a directory name collision), zetetic-team-subagents, and hypermnesia-mcp-viz. The marketplace name stays cortex-plugins: it is the brand-level umbrella, while hypermnesia-mcp is one package inside it.",
"version": "4.23.5"
},
"plugins": [
{
"name": "hypermnesia-mcp",
"source": "./",
"description": "Cortex — persistent memory and cognitive profiling for Claude Code (renamed from the 'cortex' plugin in v4.15.0 to match the PyPI/MCP-registry identity hypermnesia-mcp) — thermodynamic memory with heat/decay, intent-aware retrieval, biological plasticity, codebase intelligence, and cognitive profiling. 57 MCP tools (60 with the optional ai-architect-mcp-codebase + ai-architect-mcp-spec integrations) with enriched schemas (visualization extracted to the standalone Hypermnesia MCP Viz server). PostgreSQL + pgvector in CLI mode; automatic SQLite fallback in Cowork/sandboxed mode. v3.17.0 — autonomous per-project wiki: SessionStart auto-spawns a 6-hour consolidate cycle; a headless `claude -p` worker drains the curation-gap queue, calls codebase-intelligence MCP tools to ground each section in the real call graph, and authors missing anchor pages (architecture / services / api / data-flow / operations / decisions / PRD) per project from the source tree. 15 canonical scopes × 13 file sections; per-project dashboards under `wiki/_dashboards/`. Mermaid diagrams have a 🔍 lens with zoom + pan. Workflow graph with caller-qualified CALLS chains rendering full method-to-method dependencies (native tree-sitter, no AP required). Side panel humanized for non-technical users. Ingests codebase analysis (ai-architect-mcp-codebase) and PRDs (ai-architect-mcp-spec) into The plugins it lists here
This marketplace lists 2 plugins kept in the same repository. Each has its own page, its own measurements and its own install command.
What ships with it
1 file beside marketplace.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 22d ago Changed 969cbaee0642
- 23d ago Changed a6a0f5f4e92a
- 28d ago Changed bc4184c87086
- 29d ago Changed cd99f00bf74f
- 1mo ago Changed 14f66c24f0c5
- 1mo ago Changed f138d80e93f1
- 1mo ago Changed 4e269f9d6bfb
- 1mo ago Changed 20d34c7093b9
- 1mo ago Changed 1beda1e1f989
- 1mo ago First seen · 136 lines scan A 1bb3fb7215ae
cortex-plugins marketplace is a plugin published in the GitHub repository cdeust/Cortex (75 stars, last pushed today), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
prism-coder
Your coding agent forgets everything between sessions. Prism gives it a memory that sticks: your decisions, open TODOs, and changed files, restored the moment you return. It goes past a notes store — associative recall surfaces related past work, drift detection catches a long session wandering off-goal, and an…
papi
Persistent project management inside your AI coding tool. PAPI plans what to build next, tracks every decision, and keeps projects coherent across sessions — so a new session starts where the last one left off instead of from nothing.
inspeximus
Self-correcting memory for Claude Code. Facts you correct stay corrected, deletions leave a signed receipt you can verify offline, and storing something never calls a model. Also ships the checks: erasureresidue asks whether the bytes actually went — on any store, not just this one.
mnemo-mcp
Persistent AI memory — store, search, and recall knowledge across sessions.
synapse-mcp
Persistent AST knowledge graph and safe writes for AI coding agents across 50+ languages. 100% local — no cloud indexing, no telemetry.
stickies
A persistent sticky-note layer for Claude Code. Claude writes durable facts (decisions, blockers, preferences, context, todos) during a session; they survive resets and are injected back into context on the next start.