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/Pavlovj/mind-wiki-mcpWrote 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/pavlovj/mind-wiki-mcp/mind-wiki-mcp)<a href="https://agentmods.dev/plugins/pavlovj/mind-wiki-mcp/mind-wiki-mcp"><img src="https://agentmods.dev/badge/plugins/pavlovj/mind-wiki-mcp/mind-wiki-mcp.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
mind-wiki-mcp 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 7d 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": "mind-wiki-mcp",
"description": "MCP server for mind-wiki — access your personal knowledge wiki from any directory or Claude Desktop. Exposes query, stats, lint, review, and browse tools.",
"version": "0.1.0",
"author": {
"name": "pavlovj",
"url": "https://github.com/pavlovj"
},
"homepage": "https://github.com/pavlovj/mind-wiki-mcp",
"repository": "https://github.com/pavlovj/mind-wiki-mcp",
"license": "MIT",
"keywords": [
"mcp",
"mind-wiki",
"knowledge-base",
"claude-desktop",
"second-brain"
]
}
What it installs
The manifest is a name and a version. 1 MCP server 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.
- 7d ago First seen · 20 lines scan A ba67f116e78d
mind-wiki-mcp is a plugin published in the GitHub repository Pavlovj/mind-wiki-mcp (0 stars, last pushed 5mo 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.
claude-bestpractice
Enforcement, memory and parallel-session coordination for solo founders running several Claude Code sessions on one repository.