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 MongLong0214/commitlorenpx agentmods add plugins/monglong0214/commitlore/marketplacegit clone --depth 1 https://github.com/MongLong0214/commitloreGrade A, and why
commitlore 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
{
"name": "commitlore",
"owner": {
"name": "MongLong0214",
"url": "https://github.com/MongLong0214"
},
"description": "Recorded decisions from git history, delivered to a coding agent before it edits.",
"plugins": [
{
"name": "commitlore",
"source": "./",
"displayName": "CommitLore",
"description": "Constraints, alternatives already ruled out, and warnings left by whoever was here last — injected before the agent edits the path they cover. Records are ordinary git trailers: they survive rebase and rename, and squash keeps them only when `commitlore squash-preserve` or its GitHub Action runs.",
"author": {
"name": "MongLong0214",
"url": "https://github.com/MongLong0214"
},
"homepage": "https://github.com/MongLong0214/commitlore#readme",
"repository": "https://github.com/MongLong0214/commitlore",
"license": "MIT",
"category": "development",
"keywords": ["git", "trailers", "decisions", "memory", "context", "guard"],
"tags": ["git", "context", "memory", "hooks", "mcp"]
}
]
}
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.
- yesterday First seen · 27 lines scan A 9177ecdda4a0
commitlore is a plugin published in the GitHub repository MongLong0214/commitlore (9 stars, last pushed 3d 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
claude-plugin
Memory for AI coding agents: your own past sessions, recalled before you ask.
iai-pme
The personal memory engine for AI coding assistants — local, encrypted, verbatim.
iai-memory
Persistent local memory for your assistant: every turn captured verbatim, relevant memory injected at session start and before each turn, and fifteen memory tools over MCP. Requires the iai-pme package (pip install iai-pme).
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.
perenna
A lightweight, Git-backed permanent memory for AI agents.