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 ikotelkin/claude-skillsnpx agentmods add plugins/ikotelkin/claude-skills/working-memorygit clone --depth 1 https://github.com/ikotelkin/claude-skillsWrote 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/ikotelkin/claude-skills/working-memory)<a href="https://agentmods.dev/plugins/ikotelkin/claude-skills/working-memory"><img src="https://agentmods.dev/badge/plugins/ikotelkin/claude-skills/working-memory.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
working-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 4d 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": "working-memory",
"displayName": "Working Memory",
"version": "1.0.0",
"description": "A project's mid-term memory: a WORKING.md file in the repo that holds the current stage's state — decision log, dead ends, next steps — so it survives context compaction and new sessions, and gets distilled into long-term memory at stage end.",
"author": {
"name": "Ivan Kotelkin",
"url": "https://github.com/ikotelkin"
},
"homepage": "https://github.com/ikotelkin/claude-skills",
"repository": "https://github.com/ikotelkin/claude-skills",
"license": "MIT",
"skills": [
"."
]
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 147 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.
- 4d ago First seen · 17 lines scan A 5fd73007c8e6
working-memory is a plugin published in the GitHub repository ikotelkin/claude-skills (2 stars, last pushed 11d 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
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.
ctx
Persistent memory for Claude Code agents. Stores decisions, patterns, and knowledge in a structured graph database that persists across sessions.