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/LaserPhaser/claude-ltmWrote 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/laserphaser/claude-ltm/marketplace)<a href="https://agentmods.dev/plugins/laserphaser/claude-ltm/marketplace"><img src="https://agentmods.dev/badge/plugins/laserphaser/claude-ltm/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/laserphaser/claude-ltm/marketplace"><img src="https://agentmods.dev/badge/plugins/laserphaser/claude-ltm/marketplace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
claude-ltm-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 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": "claude-ltm-marketplace",
"owner": {
"name": "LaserPhaser",
"email": "[email protected]"
},
"metadata": {
"description": "Long-term memory plugin for Claude Code",
"version": "1.0.0"
},
"plugins": [
{
"name": "claude-ltm",
"description": "Long-term memory for Claude Code — persist project decisions across sessions",
"version": "1.0.0",
"source": {
"source": "url",
"url": "https://github.com/LaserPhaser/claude-ltm.git"
}
}
]
}
The plugins it lists here
This marketplace lists 1 plugin 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.
- 1mo ago First seen · 23 lines scan A e76e0e29ccae
claude-ltm-marketplace is a plugin published in the GitHub repository LaserPhaser/claude-ltm (4 stars, last pushed 6mo ago), 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
hippo-memory
Make your agent's memory work like a brain. Hippo is long-term memory for coding agents.
knowledge-and-memory
Research methodology, corpus search, persistent memory, iterative workflows, and project knowledge management.
agentcall
Let your AI agent join Google Meet, Zoom, or Microsoft Teams as a speaking, listening, presenting participant — works with Claude Code, Codex, Gemini CLI, and 30+ other agents.
emem
Shared, verifiable memory for AI agents. Two layers, one trust surface. Earth-scale fact substrate: every patch of ground gets a 64-bit address (cell64, about 9.55 m), and every measurement at that cell is a signed fact keyed by (cell, band, tslot), ed25519-signed by the responder over the blake3 of its canonical CBOR.
emem-signer
A local signer for emem memory writes. It holds your Ed25519 signing key, given as a sensitive plugin option, and signs only the writes you compose. Optional: install it beside the emem plugin when you want to write signed notes; reading emem needs no key.
emem
Verifiable shared memory for AI agents: resolve a place to one canonical address, recall Ed25519-signed Earth-observation facts, and hand another agent a token it can check offline. Reads need no key; the data is maintained by machines (satellites, sensors, open-data connectors), and agents can publish their own…