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 arimxyer/doc-manager-mcpnpx agentmods add plugins/arimxyer/doc-manager-mcp/plugingit clone --depth 1 https://github.com/arimxyer/doc-manager-mcpGrade A, and why
doc-manager 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 yesterday.
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": "doc-manager",
"version": "1.2.6",
"description": "Documentation lifecycle management integration for Claude Code. Provides proactive documentation health monitoring, automated sync workflows, quality assessment against 7 professional criteria, and intelligent agent coordination through the doc-manager MCP server.",
"author": {
"name": "arimxyer",
"email": "[email protected]",
"url": "https://github.com/arimxyer/doc-manager-mcp"
},
"license": "MIT",
"homepage": "https://github.com/arimxyer/doc-manager-mcp",
"repository": "https://github.com/arimxyer/doc-manager-mcp.git",
"keywords": ["documentation", "docs", "sync", "validation", "quality", "mcp", "doc-management", "technical-writing", "api-docs"],
"commands": ["./commands"],
"agents": ["./agents/doc-expert.md", "./agents/doc-writer.md"],
"skills": "./skills",
"mcpServers": ["./.mcp.json"]
}
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.
- yesterday First seen · 19 lines scan A 9dec1d1f6c5d
doc-manager is a plugin published in the GitHub repository arimxyer/doc-manager-mcp (6 stars, last pushed 7mo 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
markdown-vault-mcp
Generic markdown vault MCP with hybrid search.
docpull
Pull public web sources into Claude Code. Indexes static and server-rendered sites as local Markdown with conditional-GET caching, then exposes them as MCP tools. Local, browser-free, no API keys.
doc-bridge
Fail closed before Claude edits the wrong files: resolve the right docs, ownership boundaries, edit roots, and checks for each change.
jdocmunch-mcp
Token-efficient MCP server for structured documentation retrieval via section-level indexing.
telawiki
tela — the markdown-native team wiki your agents can read and write.
tela
Connect Claude Code to your tela wiki: semantic research with citations over your team's docs, plus authoring into rich pages, spreadsheets with real formulas, and presentable decks.