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/Johnnybyzhang/post-planInstalling this writes the configuration, not the program: `node` runs a file from the repository, so clone it first and make the path in the command match where you put it.
Wrote 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/mcp/johnnybyzhang/post-plan/post-plan-post-plan)<a href="https://agentmods.dev/mcp/johnnybyzhang/post-plan/post-plan-post-plan"><img src="https://agentmods.dev/badge/mcp/johnnybyzhang/post-plan/post-plan-post-plan/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/mcp/johnnybyzhang/post-plan/post-plan-post-plan"><img src="https://agentmods.dev/badge/mcp/johnnybyzhang/post-plan/post-plan-post-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
post-plan 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
{
"post-plan": {
"command": "node",
"args": [
"./mcp/server.mjs"
],
"cwd": ".",
"tool_timeout_sec": 30
}
}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 · 10 lines scan A dc5e9ffec7c2
post-plan is an MCP server published in the GitHub repository Johnnybyzhang/post-plan (0 stars, last pushed 3mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. 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 mcp servers, from other repositories
gw
MCP server "gw" as configured in rahilp/second-brain-cloudflare. Launched with gw mcp.
davflare
MCP server "davflare", hosted remotely at drive.example.com, as configured in fanchenggang/Davflare.
cloudflare-docs
MCP server "cloudflare-docs", hosted remotely at docs.mcp.cloudflare.com, as configured in louisbrulenaudet/monorepo-template.
cloudflare-observability
MCP server "cloudflare-observability", hosted remotely at observability.mcp.cloudflare.com, as configured in louisbrulenaudet/monorepo-template.
nodrix
Read live and historical IoT telemetry and actuate ESP32/Arduino hardware from a backend you host. Remote server at {host}.
wsc
Prose linter + AI-slop detector: weasel words, passive voice, hedging, and research-cited AI tells. Runs locally from the wsc-mcp npm package.