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 commands/xbim08/awesome-claude-code-plugins/claude-desktop-extensiongit clone --depth 1 https://github.com/xbim08/awesome-claude-code-pluginsWrote 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/xbim08/awesome-claude-code-plugins/claude-desktop-extension)<a href="https://agentmods.dev/commands/xbim08/awesome-claude-code-plugins/claude-desktop-extension"><img src="https://agentmods.dev/badge/commands/xbim08/awesome-claude-code-plugins/claude-desktop-extension.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.1 | $0.00023 | $0.00354 |
| Opus 5 | $0.00012 | $0.00177 |
| Sonnet 5 | $0.00005 | $0.00071 |
| Haiku 4.5 | $0.00002 | $0.00035 |
Grade A, and why
claude-desktop-extension 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 6d 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.
This is a copy
100% identical to claude-desktop-extension — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
I want to build this as a Desktop Extension, abbreviated as "DXT". Please follow these steps:
-
Read the specifications thoroughly:
- https://github.com/anthropics/dxt/blob/main/README.md - DXT architecture overview, capabilities, and integration patterns
- https://github.com/anthropics/dxt/blob/main/MANIFEST.md - Complete extension manifest structure and field definitions
- https://github.com/anthropics/dxt/tree/main/examples - Reference implementations including a "Hello World" example
-
Create a proper extension structure:
- Generate a valid manifest.json following the MANIFEST.md spec
- Implement an MCP server using @modelcontextprotocol/sdk with proper tool definitions
- Include proper error handling and timeout management
-
Follow best development practices:
- Implement proper MCP protocol communication via stdio transport
- Structure tools with clear schemas, validation, and consistent JSON responses
- Make use of the fact that this extension will be running locally
- Add appropriate logging and debugging capabilities
- Include proper documentation and setup instructions
-
Test considerations:
- Validate that all tool calls return properly structured responses
- Verify manifest loads correctly and host integration works
Generate complete, production-ready code that can be immediately tested. Focus on defensive programming, clear error messages, and following the exact DXT specifications to ensure compatibility with the ecosystem.
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.
- 6d ago First seen · 32 lines · 23 tokens per session scan A 0d69a735aeb5
claude-desktop-extension is a command published in the GitHub repository xbim08/awesome-claude-code-plugins (10 stars, last pushed today), licensed Apache-2.0. It adds 23 tokens to every session and 354 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to claude-desktop-extension, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
debate
The debate — Claude and Codex argue a design decision from opposite corners, you arbitrate.
remember
Save the current session to persistent context memory.
decide
Forces structured decision-making and creates an auditable Agent Decision Record (AgDR).
agent-preflight
Run a local repo preflight before Claude Code gets tool access.
skip-reflect
Discard queued learnings without processing.
claude-desktop-extension
This command provides the context necessary for Claude Code to create the Desktop Extension or .dxt file of an MCP.