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/open-latch/latchWrote 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/open-latch/latch/marketplace)<a href="https://agentmods.dev/plugins/open-latch/latch/marketplace"><img src="https://agentmods.dev/badge/plugins/open-latch/latch/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/open-latch/latch/marketplace"><img src="https://agentmods.dev/badge/plugins/open-latch/latch/marketplace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
open-latch 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 4d 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": "open-latch",
"owner": {
"name": "open-latch",
"url": "https://github.com/open-latch"
},
"description": "Decision continuity for coding agents.",
"plugins": []
}
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 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.
- 4d ago First seen · 10 lines scan A eca6deacf033
open-latch marketplace is a plugin published in the GitHub repository open-latch/latch (9 stars, last pushed 4d 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-10-12.
Other plugins, from other repositories
ctx
Fast local search and 'git blame' for agent sessions.
palimem marketplace
Plugin marketplace listing 1 plugin: memory-service.
memory-service
Local-first governed memory for Claude Code via MCP and lifecycle hooks.
krimto
Open-source memory for AI coding agents you own in git — governed by a real user→team→org hierarchy, not a vendor database. Solo to team. Apache-2.0.
agent-recall
Persistent memory for AI coding agents. SQLite knowledge graph with scoped entities, MCP tools, and LLM-summarized briefings.
deja
deja-vu memory for Gemini CLI: the coding sessions already on your disk — Gemini CLI, Claude Code, Codex, Cursor and thirty-eight more — searchable and recalled, including work from before it was installed.