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/yul761/StateCoreWrote 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/yul761/statecore/claude-code)<a href="https://agentmods.dev/plugins/yul761/statecore/claude-code"><img src="https://agentmods.dev/badge/plugins/yul761/statecore/claude-code/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/yul761/statecore/claude-code"><img src="https://agentmods.dev/badge/plugins/yul761/statecore/claude-code.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
statecore 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 21d 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": "statecore",
"version": "1.0.0",
"description": "Auditable project memory for Claude Code: captures every prompt and reply into StateCore, re-injects the project's memory at session start and after compaction, and exposes the remember/recall/facts/why/forget/handoff tools.",
"author": { "name": "yul761", "url": "https://github.com/yul761/StateCore" },
"homepage": "https://github.com/yul761/StateCore/tree/main/plugins/claude-code",
"repository": "https://github.com/yul761/StateCore",
"license": "MIT",
"keywords": ["memory", "statecore", "mcp", "hooks"]
}
What it installs
The manifest is a name and a version. 4 hooks travel with it, and installing the plugin installs all of 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.
- 21d ago First seen · 11 lines scan A 6616f86e233c
statecore is a plugin published in the GitHub repository yul761/StateCore (1 stars, last pushed 15d 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-09-24.
Other plugins, from other repositories
openloomi
Connect Claude Code to your local OpenLoomi runtime. One-command install, mirror Claude's lifecycle onto the Loomi Pet, and auto-archive every Stop into your OpenLoomi memory. Talks to your local OpenLoomi over HTTP and the OpenLoomi helper CLI. AI provider config is owned by OpenLoomi itself — this plugin never reads.
Elpis
Provider-neutral terminal agent shell for controlled context, persistent memory, safe execution, and session continuity.
titen-memory
Use Titen's evidence-grounded collaborative memory. The local stdio mode needs no configuration; a served Titen endpoint is the alternative for a shared store.
yantrikdb
Cognitive memory for AI agents — semantic recall, a knowledge graph, contradiction detection and procedural learning. Local-first: one SQLite file, no account, no telemetry.
mnemos-memory
Biomimetic long-term memory for Claude Code with surprisal gating, mutable reconsolidation, affective routing, and sleep consolidation.
memos
Local-first persistent memory: store durable facts, recall them in any session. Zero cloud, zero telemetry, SQLite-backed.