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/asanabrial/leteoWrote 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/asanabrial/leteo/claude-code)<a href="https://agentmods.dev/plugins/asanabrial/leteo/claude-code"><img src="https://agentmods.dev/badge/plugins/asanabrial/leteo/claude-code/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/asanabrial/leteo/claude-code"><img src="https://agentmods.dev/badge/plugins/asanabrial/leteo/claude-code.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
leteo 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 10d 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": "leteo",
"description": "Persistent memory for AI coding agents. Survives across sessions and compactions.",
"version": "0.3.0",
"author": {
"name": "Alexis Sanabria Lopez"
},
"homepage": "https://github.com/asanabrial/leteo",
"repository": "https://github.com/asanabrial/leteo",
"license": "MIT"
}
What it installs
The manifest is a name and a version. 1 skill, 4 hooks, 1 MCP server travel with it, and installing the plugin installs all of them — 38 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.
- 10d ago Changed 8fe230e0caaa
- 1mo ago Changed 50af490bea0a
- 1mo ago First seen · 12 lines scan A 5bc8fc3f19e5
leteo is a plugin published in the GitHub repository asanabrial/leteo (2 stars, last pushed yesterday), 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-31.
Other plugins, from other repositories
ownmem
Git-native project memory for AI coding agents, with deterministic local recall, evidence gates, and layered delivery that quotes, points, or abstains.
ownmem
Git-native project memory for AI coding agents, with deterministic local recall, evidence gates, and layered delivery that quotes, points, or abstains.
memex
Zettelkasten-based agent memory system with bidirectional links.
agent-memory
The agent-memory skill for Claude Desktop — Chat, Cowork and the Code tab — and Claude Code: when to look up the user's earlier conversations and project files through the cam MCP server. Needs cam installed; with this plugin on, cam install leaves out its own copy in /.claude/skills.
kage
Kage manages your memory and agents. It briefs and runs agents in isolated git worktrees for a single run or a multi-wave goal, re-runs the checks itself instead of trusting the agent's report, and remembers what it learns so each brief is smarter than the last.
failure-memory marketplace
Local, cross-agent memory for learning from real failures without treating requirement changes as mistakes.