Wonderwhy-er/DesktopCommanderMCP is an MCP server that lets AI clients search and edit files, run terminal commands, and manage computer processes. It is used to give coding agents practical control over a local development environment through chat. The catalogue add-ons extend or configure this server and its agent workflows.
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/wonderwhy-er/DesktopCommanderMCPWrote 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/rules/wonderwhy-er/desktopcommandermcp/desktop-commander-default)<a href="https://agentmods.dev/rules/wonderwhy-er/desktopcommandermcp/desktop-commander-default"><img src="https://agentmods.dev/badge/rules/wonderwhy-er/desktopcommandermcp/desktop-commander-default/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/rules/wonderwhy-er/desktopcommandermcp/desktop-commander-default"><img src="https://agentmods.dev/badge/rules/wonderwhy-er/desktopcommandermcp/desktop-commander-default.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.00094 | $0.00094 |
| Opus 5.5 | $0.00038 | $0.00038 |
| Sonnet 5.5 | $0.00019 | $0.00019 |
| Haiku 4.5 | $0.00009 | $0.00009 |
Grade A, and why
desktop-commander-default 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- desktop-commander-default — 100% identical, 0 lines differ
- desktop-commander-default — 100% identical, 0 lines differ
What it actually says
For local filesystem, terminal, process, search, and workspace operations, prefer Desktop Commander MCP, especially for persistent shells, long-running processes, file reads, structured documents, large local data files, SSH workflows, and process inspection.
You can check the desktop-commander-overview SKILL for Desktop Commander MCP tool guidance.
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 · 9 lines · 94 tokens per session scan A 341101b29455
desktop-commander-default is a cursor rule published in the GitHub repository wonderwhy-er/DesktopCommanderMCP (10,134 stars, last pushed yesterday), licensed MIT. It adds 94 tokens to every session, about $0.0004 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-30.
Other cursor rules, from other repositories
agent-development
Guidelines for developing pydantic-ai agents, tools, and handlers.
project-overview
Core project architecture, patterns, and conventions for the AI Documentation Generator.
code-patterns
Python code style and recurring patterns (config, logging, errors, paths).
shadcn-tailwind-guide
A guide to building new components with shadcn/ui and Tailwind CSS, a utility-based system for styling interfaces.
1c-extension-specifics
A set of rules for developing 1C configuration extensions, which add or alter behaviour without directly changing the main configuration. It covers event hooks, reused code, XML exports, and extension builds.
simplicity
Simplicity - smallest correct diff; reuse, platform, installed deps before new code; no speculative abstraction.