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/stefan-jansen/claude-code-toolkitWrote 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/stefan-jansen/claude-code-toolkit/memory)<a href="https://agentmods.dev/plugins/stefan-jansen/claude-code-toolkit/memory"><img src="https://agentmods.dev/badge/plugins/stefan-jansen/claude-code-toolkit/memory/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/stefan-jansen/claude-code-toolkit/memory"><img src="https://agentmods.dev/badge/plugins/stefan-jansen/claude-code-toolkit/memory.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
memory 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 1mo 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": "memory",
"version": "1.0.0",
"description": "Active memory management and maintenance for Claude Code framework",
"author": {
"name": "Claude Code Framework"
},
"keywords": [
"memory",
"maintenance",
"context",
"management"
],
"commands": [
"./commands/index.md",
"./commands/memory-gc.md",
"./commands/memory-review.md",
"./commands/memory-update.md",
"./commands/performance.md"
],
"repository": "https://github.com/yourusername/claude-code-plugins",
"license": "MIT"
}
What it installs
The manifest is a name and a version. 6 commands travel with it, and installing the plugin installs all of them — 53 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.
- 1mo ago First seen · 24 lines scan A 0eafccc0670c
memory is a plugin published in the GitHub repository stefan-jansen/claude-code-toolkit (90 stars, last pushed 3mo 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-30.
Other plugins, from other repositories
ctx
Fast local search and 'git blame' for agent sessions.
context-guard
Per-session context-window observability. A mod writes each session's context-window figures to a snapshot file and shows the person a toast and a transcript line when the context zone (smart, acceptable or dumb, from bands in zones.json) worsens; with modelnotices on (off by default) it also tells Claude the zone at.
claude-memory
Keeps a repo's Claude Code memory layer healthy and under your control, against criteria derived from official Claude Code documentation. The audit skill checks the instruction/memory layer (CLAUDE.md, a root AGENTS.md, CLAUDE.local.md, .claude/rules/, auto-memory) with a deterministic script-backed spine plus…
harness-memory
Keeps a repo's Claude Code memory layer healthy, against criteria from official Claude Code docs. audit checks CLAUDE.md, a root AGENTS.md, CLAUDE.local.md, .claude/rules/, and auto-memory for structure, size, placement, and index integrity, with scripted and judgment checks. stateless inspects, disables, and (after…
session-tools
Session productivity — cost/token monitoring (ccboard), voice refinement, context catchup, MCP integration templates, and 11 session hooks.
mem9
Persistent cloud memory for Claude Code. Auto-loads memories on session start, auto-saves on stop, with on-demand store/recall skills.