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 andresanemic/lore-pluginnpx agentmods add plugins/andresanemic/lore-plugin/marketplacegit clone --depth 1 https://github.com/andresanemic/lore-pluginGrade A, and why
lore-plugin 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 2d 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": "lore-plugin",
"owner": {
"name": "andresanemic"
},
"metadata": {
"description": "The Lore marketplace — provider-neutral project criterion for AI agents.",
"version": "2.4.4"
},
"plugins": [
{
"name": "lore",
"source": "./",
"description": "Local fine-tuning for your own tasks, except the one doing the training is you. Operate Lore with use-lore, brainstorming-lore, create-area, create-project, create-bot, save-to-lore, and transmute-lore."
}
]
}
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.
- 2d ago First seen · 18 lines scan A af578635a85c
lore-plugin is a plugin published in the GitHub repository andresanemic/lore-plugin (6 stars, last pushed 2d 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
anishfyi-trove
A personal knowledge trove for Claude Code, by anishfyi. Capture durable learnings as you work and reload them every session.
trove
Repository memory for Claude Code: index symbols and architecture, progressively retrieve context beyond the context window, and capture durable engineering decisions in a personal trove.
aria-knowledge
ARIA — Applied Reasoning and Insight Architecture. Persistent human-governed knowledge for Claude Code via a five-phase lifecycle: capture → govern → promote → apply → refresh. Stages session insights/decisions/feedback into review backlogs, promotes approved items to a tag-indexed markdown base, and applies them via…
aria-knowledge
ARIA — Applied Reasoning and Insight Architecture. Knowledge management, decision discipline, codebase understanding, plan pre-mortems, and release retrospectives for Claude Code.
aria-cowork
Knowledge management for Claude Cowork — capture, organize, and apply durable knowledge across your work, available in any project workspace via a persistent folder grant. Companion to aria-knowledge for Claude Code; both share one knowledge folder so insights flow between conversational and engineering work. Default…
aria-probe
Validation probe for aria-cowork. Tests whether a Cowork plugin can read and write the user-attached knowledge folder, verifies bidirectional access with aria-knowledge in Code, and (v0.2.0) tests whether Cowork can read the existing aria-knowledge config at /.claude/aria-knowledge.local.md when /.claude/ is attached.