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/jolliai/jolli-claude-pluginWrote 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/jolliai/jolli-claude-plugin/jolli)<a href="https://agentmods.dev/plugins/jolliai/jolli-claude-plugin/jolli"><img src="https://agentmods.dev/badge/plugins/jolliai/jolli-claude-plugin/jolli.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
jolli 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 8d 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.
This is a copy
100% identical to jolli — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{
"name": "jolli",
"displayName": "Jolli Memory",
"version": "1.0.6",
"description": "Automatically captures and generates project memory from your development work — team-shareable and synced across devices, so you can recall and search past decisions and context across sessions and agents. Backed by the jolli CLI bundled as an MCP server.",
"author": { "name": "jolli.ai", "url": "https://jolli.ai" },
"homepage": "https://jolli.ai",
"license": "Apache-2.0",
"keywords": ["memory", "recall", "pr", "git", "context"]
}
What it installs
The manifest is a name and a version. 4 skills, 4 commands, 1 hook, 1 MCP server travel with it, and installing the plugin installs all of them — 320 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.
- 8d ago First seen · 11 lines scan A 607b3f29d03f
jolli is a plugin published in the GitHub repository jolliai/jolli-claude-plugin (2 stars, last pushed 9d 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. It is 100% identical to jolli, differing in 0 lines, and is treated as a copy.
Other plugins, from other repositories
knowledge-and-memory
Research methodology, corpus search, persistent memory, iterative workflows, and project knowledge management.
@tekmidian/pai
Personal AI Infrastructure — persistent memory, session continuity, and knowledge graph for Claude Code.
claude-mega-brain
OKF-powered knowledge context for Claude Code — injects your project knowledge base at every session.
tree-ring-memory
Local-first memory lifecycle, project bootstrap, and receipt-backed harness guidance for Claude Code using Tree Ring Memory v0.15+.
vault-template
Personal Knowledge Management system for Obsidian with AI-powered workflows, goal tracking, and productivity coaching.
claude-bestpractice
Enforcement, memory and parallel-session coordination for solo founders running several Claude Code sessions on one repository.