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.
/plugin marketplace add rekal-dev/rekal-clinpx agentmods add plugins/rekal-dev/rekal-cli/plugingit clone --depth 1 https://github.com/rekal-dev/rekal-cliGrade A, and why
rekal 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 yesterday.
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
{
"$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
"name": "rekal",
"displayName": "Rekal Memory",
"version": "0.3.4",
"description": "Memory for your coding agent. Rekal saves every AI session transcript raw and append-only — no summaries to rot — then recalls the reasoning behind any change: why an approach was chosen, what was tried, what was rejected. Agent agnostic: Claude Code, Cursor, Codex, Gemini, Copilot, Kiro and OpenCode sessions all land in one ledger. Retrieval reasons at query time over the real record, with keyword and semantic search running locally — embedding is local, so there is no server, no account, no external memory service. Git is the transport: memory travels with your repo on push and reaches your team when work merges. Persistent cross-session context that maintains itself.",
"author": {
"name": "Rekal",
"url": "https://rekal.dev/"
},
"homepage": "https://rekal.dev/",
"repository": "https://github.com/rekal-dev/rekal-cli",
"license": "Apache-2.0",
"keywords": [
"memory",
"recall",
"git",
"sessions",
"context",
"ledger"
]
}
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.
- yesterday First seen · 23 lines scan A 3ff94f42427e
rekal is a plugin published in the GitHub repository rekal-dev/rekal-cli (140 stars, last pushed 28d 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-30.
Other plugins, from other repositories
emulo
Emulo: mine your local AI coding session logs into a personal profile your agent loads before every task.
emulo
Mine real AI coding sessions into a bounded, evidence-backed personal layer.
agentmap
Single-plugin marketplace for agentmap — the queryable, PageRank-ranked ts-morph repo map for TS/JS coding agents.
agentmap
98% fewer context tokens for your coding agent to find code — a queryable, PageRank-ranked ts-morph import/symbol map for TS/JS repos. Bundles the PreToolUse grep nudge, the navigation skill, and a stdio MCP server exposing 11 query tools including a compiler-accurate call graph, BM25 lexical search, plus CLI-only Mer.
memex
Zettelkasten-based agent memory system with bidirectional links.
memex
Zettelkasten-based agent memory system with bidirectional links.