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/Onplana/onplana-mcp-serverWrote 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/commands/onplana/onplana-mcp-server/onplana-connect)<a href="https://agentmods.dev/commands/onplana/onplana-mcp-server/onplana-connect"><img src="https://agentmods.dev/badge/commands/onplana/onplana-mcp-server/onplana-connect/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/commands/onplana/onplana-mcp-server/onplana-connect"><img src="https://agentmods.dev/badge/commands/onplana/onplana-mcp-server/onplana-connect.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00014 | $0.00547 |
| Opus 5.5 | $0.00006 | $0.00219 |
| Sonnet 5.5 | $0.00003 | $0.00109 |
| Haiku 4.5 | $0.00001 | $0.00055 |
Grade A, and why
onplana-connect 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 22d 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sign this Claude Code session in to Onplana's MCP server and confirm the connection before reporting success.
How the server gets here
The plugin declares the server in its own .mcp.json, pointing at
https://mcp.onplana.com/mcp, so installing the plugin is enough to add it.
It appears in /mcp as plugin:onplana:onplana. If the person already
added that URL themselves, Claude Code keeps their entry and treats the
plugin's as a duplicate, so there is still only one set of tools.
Steps
-
Sign in. Ask the person to run
/mcp, choose the Onplana server, and complete the browser sign-in. The token is issued to the Onplana organization they sign in as, and it lasts 90 days. -
Verify rather than assume. Call
whoamiand report the account and organization it returns. If the tool list is empty or the call fails, the connection is not usable yet, so say so plainly instead of continuing. -
Only if the server is missing from
/mcp(for example, the plugin's server was toggled off), add it by hand, then go back to step 1:claude mcp add --transport http --scope user onplana https://mcp.onplana.com/mcp
What they get
Roughly 265 tools, scoped to the signed-in organization and filtered by that person's own role and plan. Reads and writes both go through the same permission checks the web app uses, and every write is audited.
Two skills ship with this plugin:
- onplana:onplana-project-planner turns a goal or a brief into an executable plan: a plan document attached to the project, then a task tree with dates, dependencies, owners and test cases.
- onplana:onplana-autonomous-agent runs an existing plan: claim a task, work it, record progress and evidence, resolve or hand it back, then take the next one.
Suggest the planner skill when they want a plan built, and the autonomous skill when a plan already exists and they want it executed.
If they do not have an account
Onplana has a free tier and the MCP server is available on every plan, including free. Point them at https://onplana.com and continue once they can sign in.
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.
- 22d ago Changed · +1 lines · -1 tokens per session 9c821f8d6aec
- 1mo ago First seen · 54 lines · 15 tokens per session scan A 237bec575c5f
onplana-connect is a command published in the GitHub repository Onplana/onplana-mcp-server (4 stars, last pushed 7d ago), licensed MIT. It adds 14 tokens to every session and 547 once invoked, about $0.0001 per session on Opus 5.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-31.
Other commands, from other repositories
staff-event
Build a complete event staffing plan (configured-market match, W-2 rates, tier-based lead time, compliance) and prepare a buyer-submitted quote form.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.