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 abstractwebunit/markdown-publish-pluginnpx agentmods add plugins/abstractwebunit/markdown-publish-plugin/markdown-publish-plugingit clone --depth 1 https://github.com/abstractwebunit/markdown-publish-pluginGrade A, and why
markdown-publish 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": "markdown-publish",
"version": "0.1.0",
"description": "Publish your Obsidian/Markdown vault as a static site in one chat, then let AI read your notes via MCP.",
"author": {
"name": "abstractwebunit"
},
"homepage": "https://abstractwebunit.github.io/markdown-publish-docs/",
"repository": "https://github.com/abstractwebunit/markdown-publish-plugin",
"keywords": [
"obsidian",
"markdown",
"static-site-generator",
"digital-garden",
"publish",
"mcp"
],
"mcpServers": {
"markdown-publish": {
"command": "node",
"args": ["${CLAUDE_PLUGIN_ROOT}/mcp/server.mjs"],
"env": {
"MARKDOWN_PUBLISH_SOURCE": "${MARKDOWN_PUBLISH_SOURCE}"
}
}
}
}
What ships with it
1 file beside plugin.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 28 lines scan A 729fcd1825e7
markdown-publish is a plugin published in the GitHub repository abstractwebunit/markdown-publish-plugin (0 stars, last pushed 2mo 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
deeppapernote
Academic paper reading and Obsidian note generation skills for building a research WIKI.
mineru
Parse PDF / Office / image files into clean Markdown via MinerU — zero-dependency, AI-Native, auto-routing between the free Agent API and the token-gated Standard API, with 15 content-tool delivery sinks.
onebrain
Plugin marketplace listing 1 plugin: onebrain.
onebrain
OneBrain — Your AI Thinking Partner.
mnemonic
Pure filesystem-based memory system for Claude Code with custom ontology support.
mock-plugin
Mock plugin for testing integration.