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 skills add hybridlabor-api/bdb-dev-optimized-agent-skills --skill desktop-automation-protocolgit clone --depth 1 https://github.com/hybridlabor-api/bdb-dev-optimized-agent-skillsWrote 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/hybridlabor-api/bdb-dev-optimized-agent-skills/desktop-automation-protocol)<a href="https://agentmods.dev/skills/hybridlabor-api/bdb-dev-optimized-agent-skills/desktop-automation-protocol"><img src="https://agentmods.dev/badge/skills/hybridlabor-api/bdb-dev-optimized-agent-skills/desktop-automation-protocol/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/skills/hybridlabor-api/bdb-dev-optimized-agent-skills/desktop-automation-protocol"><img src="https://agentmods.dev/badge/skills/hybridlabor-api/bdb-dev-optimized-agent-skills/desktop-automation-protocol.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.00029 | $0.00444 |
| Opus 5 | $0.00015 | $0.00222 |
| Sonnet 5 | $0.00006 | $0.00089 |
| Haiku 4.5 | $0.00003 | $0.00044 |
Grade A, and why
desktop-automation-protocol 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 desktop-automation-protocol — 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
Desktop automation protocol (windows-computer-use-mcp)
Tool selection guide
| Goal | Tool | Example |
|---|---|---|
| Click a known button | automation_elements(click, title="Save") |
fast, needs exact title |
| Click by intent | automation_smart(click="the Save button") |
slower, finds across all windows |
| Complex multi-step | automation_mission(run="save file as PDF") |
autonomous loop with retry |
| Record + replay | automation_macro(record) → stop → replay |
repeatable sequences |
| Wait for event | automation_watch(start, "window_appears", "Update") |
event-driven triggers |
| Explore desktop | automation_smart(discover) |
get all running apps |
| Extract + chain | automation_mission(workflow, actions, store_as, dollar-ref) |
cross-app data pipeline |
Focus rules
- After automation starts, do not Alt+Tab or touch the mouse
- The target window must stay in foreground during click/type sequences
- If HITL approval appears, approve it and let the target window regain focus
- Prefer reading logs between paused steps or on a second monitor
Safety
- Read docs/SAFETY.md before production use
- Pair with virtualization-mcp for sandbox/VM isolation when running untrusted automation
- Opt-in features (face, keylogger) are off by default — enable only when needed
Mission design (automation_mission)
For run operation: provide a clear, concrete goal. The server decomposes via LLM sampling.
For workflow operation: provide explicit steps with tool, params, label, and optional store_as/dollar-ref for data chaining.
For self-healing: set app_path on steps so the mission can re-launch crashed apps.
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 · 37 lines · 29 tokens per session scan A 857216599875
desktop-automation-protocol is a skill published in the GitHub repository hybridlabor-api/bdb-dev-optimized-agent-skills (6 stars, last pushed 4d ago), licensed Apache-2.0. It adds 29 tokens to every session and 444 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 desktop-automation-protocol, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
context-preservation
State capture and restore across context window compactions. Monitors usage thresholds and serializes quality, task, and spec state for seamless continuation.
cog-braindump-capture
Capture raw thoughts with automatic domain classification and vault routing.
cog-knowledge-consolidation
Build structured knowledge frameworks from scattered vault notes with source attribution.
cog-onboarding
Personalize COG Second Brain workflow through role pack selection and vault initialization.
cog-weekly-reflection
Cross-domain pattern analysis with personal, professional, and project domain synthesis.
context-engineering
Dynamic context injection, mode switching (dev/review/research), selective loading, and strategic compaction for token optimization.