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/youdie006/sessionwikiWrote 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/youdie006/sessionwiki/plugin)<a href="https://agentmods.dev/plugins/youdie006/sessionwiki/plugin"><img src="https://agentmods.dev/badge/plugins/youdie006/sessionwiki/plugin/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/youdie006/sessionwiki/plugin"><img src="https://agentmods.dev/badge/plugins/youdie006/sessionwiki/plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
sessionwiki 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
{
"$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
"name": "sessionwiki",
"displayName": "sessionwiki session recall",
"version": "0.1.0",
"description": "Recall and reuse your past AI coding sessions as long-term memory. Searches the local sessionwiki index so the agent can find prior work, pull context, and trace which session wrote a file.",
"author": {
"name": "youdie006",
"url": "https://github.com/youdie006"
},
"homepage": "https://github.com/youdie006/sessionwiki",
"repository": "https://github.com/youdie006/sessionwiki",
"license": "MIT",
"keywords": ["memory", "sessions", "recall", "search", "context", "claude-code", "codex", "gemini-cli"]
}
What it installs
The manifest is a name and a version. 1 skill, 1 command, 1 hook travel with it, and installing the plugin installs all of them — 135 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 · 16 lines scan A edb1c45679b0
sessionwiki is a plugin published in the GitHub repository youdie006/sessionwiki (27 stars, last pushed today), 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
sessions
Skills for summarizing and recalling AI coding sessions across Claude Code, Codex, Pi, and OpenCode.
personal
Personal knowledge and finance automation — autonomous Obsidian vault management (PARA + LLM Wiki) and end-to-end corporate/personal tax preparation from Xero, bank statements, and Google Drive.
alloydb
Create, connect, and interact with an AlloyDB for PostgreSQL database and data.
unforgit-claude-code-marketplace
Claude Code plugins for Unforgit persistent repository memory.
logs-locally-plugin
Store and browse AI agent session logs locally with a SQLite database and web UI.
context-guard
Context-budget guard for long Claude Code and Codex sessions: a Stop hook enforces a per-model checkpoint protocol (mechanical stub + budgeted memory-writer subagent on Claude; a direct stub-write instruction on Codex), and a SubagentStop tracker surfaces true session spend (main thread + subagents) on Claude. Default.