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.
npx agentmods add skills/planexeorg/planexe/planexe-mcpnpx skills add PlanExeOrg/PlanExe --skill planexe-mcpgit clone --depth 1 https://github.com/PlanExeOrg/PlanExeWrote 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/skills/planexeorg/planexe/planexe-mcp)<a href="https://agentmods.dev/skills/planexeorg/planexe/planexe-mcp"><img src="https://agentmods.dev/badge/skills/planexeorg/planexe/planexe-mcp.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00036 | $0.02235 |
| Opus 5 | $0.00018 | $0.01118 |
| Sonnet 5 | $0.00007 | $0.00447 |
| Haiku 4.5 | $0.00004 | $0.00224 |
Grade A, and why
planexe-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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 362 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PlanExe MCP Skill
Access PlanExe's powerful planning capabilities directly from OpenClaw via the Model Context Protocol (MCP).
Overview
The planexe-mcp skill provides a unified interface to interact with PlanExe across three deployment scenarios:
- Cloud:
mcp.planexe.org(Stripe credits at home.planexe.org) - Remote Docker: Container on a separate machine
- Local Docker: Container on the same machine as OpenClaw
Setup by Deployment Scenario
Scenario A: Cloud-Hosted Service
Connect to the hosted PlanExe MCP service.
Configuration:
Add to your OpenClaw config or environment:
PLANEXE_MCP_URL=https://mcp.planexe.org
PLANEXE_API_KEY=your_api_key_from_planexe_account
How to Get Your API Key:
- Visit home.planexe.org
- Purchase credits via Stripe
- Generate an API key in your account dashboard
- Copy the key to your OpenClaw configuration
Scenario B: Remote Docker
Run PlanExe in Docker on a separate machine and connect remotely.
On the Remote Machine:
docker run -p 8001:8001 planexe/planexe:latest
Configuration in OpenClaw:
PLANEXE_MCP_URL=http://<remote-ip>:8001
PLANEXE_API_KEY=your_api_key
Replace <remote-ip> with your remote machine's IP address or hostname.
Scenario C: Local Docker
Run PlanExe in Docker on the same machine as OpenClaw.
Setup:
docker run -p 8001:8001 planexe/planexe:latest
Configuration in OpenClaw:
PLANEXE_MCP_URL=http://127.0.0.1:8001
PLANEXE_API_KEY=your_api_key
Invoking PlanExe Tools
The PlanExe MCP exposes nine core tools via the /mcp endpoint:
Tool 1: example_plans
Preview curated example plans with download links for reports and zip bundles.
No parameters required:
{
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"name": "example_plans",
"arguments": {}
}
}
Returns: List of example plans with title, report_url, and zip_url.
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.
- 5d ago First seen · 362 lines · 36 tokens per session scan A e68d59c0f32d
planexe-mcp is a skill published in the GitHub repository PlanExeOrg/PlanExe (398 stars, last pushed 5d ago), licensed MIT. It adds 36 tokens to every session and 2,235 once invoked, about $0.0002 per session on Opus 5. 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-30.
Other skills, from other repositories
session-rag-eval
Run and debug Chatbox session attachment RAG model evaluation with synthetic and real long-file fixtures.
designer_guide
Guidance for creating and editing designs using the designer tool.
lynkr
Universal LLM gateway with intelligent routing, Graphify code intelligence, Distill compression, routing telemetry, Code Mode, and 12+ provider support. 60-80% cost reduction for Claude Code, Cursor, and Codex.
agents_guide
Guidance for delegating focused work to child Agents.
文档协作
引导用户通过结构化的文档共同编写工作流程。当用户想撰写文档、提案、技术规范、决策文档或类似结构化内容时使用。该工作流程帮助用户高效传递上下文，通过迭代优化内容，并验证文档对读者有效。当用户提到写文档、创建提案、起草规范或类似文档任务时触发。.
data_analyst
Analyses datasets with professional rigour — statistical summaries, clear narratives, and well-chosen visualisations.