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/vedantnimbarte/kortex-memoryWrote 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/vedantnimbarte/kortex-memory/plugin)<a href="https://agentmods.dev/plugins/vedantnimbarte/kortex-memory/plugin"><img src="https://agentmods.dev/badge/plugins/vedantnimbarte/kortex-memory/plugin/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/vedantnimbarte/kortex-memory/plugin"><img src="https://agentmods.dev/badge/plugins/vedantnimbarte/kortex-memory/plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
kortex-memory 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
{
"name": "kortex-memory",
"displayName": "Kortex Memory",
"version": "0.1.0",
"description": "Persistent, governed memory for Claude Code. Remember decisions once; recall them in every future session, across every tool on the team.",
"author": {
"name": "Kortex Memory",
"url": "https://github.com/vedantnimbarte/kortex-memory"
},
"homepage": "https://github.com/vedantnimbarte/kortex-memory",
"repository": "https://github.com/vedantnimbarte/kortex-memory",
"keywords": ["memory", "mcp", "rag", "context", "recall"],
"userConfig": {
"mcp_url": {
"type": "string",
"title": "Kortex MCP endpoint",
"description": "The SSE endpoint of your Kortex MCP server, e.g. https://kortex.example.com:8765/sse. For a local `make dev` stack this is http://localhost:8765/sse.",
"default": "http://localhost:8765/sse",
"required": true
},
"api_key": {
"type": "string",
"title": "Kortex API key",
"description": "A kx_* key from `kortex key create`. Scoped to one org, so it decides which memories this machine can read and write.",
"sensitive": true,
"required": true
}
},
"mcpServers": "./.mcp.json",
"skills": "./skills/"
}
What it installs
The manifest is a name and a version. 1 skill, 1 MCP server travel with it, and installing the plugin installs all of them — 95 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 · 32 lines scan A f61804950bb4
kortex-memory is a plugin published in the GitHub repository vedantnimbarte/kortex-memory (2 stars, last pushed 1mo ago), licensed Apache-2.0. 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-31.
Other plugins, from other repositories
token-optimizer
Context-window optimization tools (caching, compression, smart file tooling) for the Gemini CLI.
openloomi
Connect Claude Code to your local OpenLoomi runtime. One-command install, mirror Claude's lifecycle onto the Loomi Pet, and auto-archive every Stop into your OpenLoomi memory. Talks to your local OpenLoomi over HTTP and the OpenLoomi helper CLI. AI provider config is owned by OpenLoomi itself — this plugin never reads.
Elpis
Provider-neutral terminal agent shell for controlled context, persistent memory, safe execution, and session continuity.
yantrikdb
Cognitive memory for AI agents — semantic recall, a knowledge graph, contradiction detection and procedural learning. Local-first: one SQLite file, no account, no telemetry.
titen-memory
Use Titen's evidence-grounded collaborative memory. The local stdio mode needs no configuration; a served Titen endpoint is the alternative for a shared store.
mnemos-memory
Biomimetic long-term memory for Claude Code with surprisal gating, mutable reconsolidation, affective routing, and sleep consolidation.