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 aloth/PowerSkills --skill desktopgit clone --depth 1 https://github.com/aloth/PowerSkillsWrote 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/aloth/powerskills/desktop)<a href="https://agentmods.dev/skills/aloth/powerskills/desktop"><img src="https://agentmods.dev/badge/skills/aloth/powerskills/desktop/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/aloth/powerskills/desktop"><img src="https://agentmods.dev/badge/skills/aloth/powerskills/desktop.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.00053 | $0.00585 |
| Opus 5.5 | $0.00021 | $0.00234 |
| Sonnet 5.5 | $0.00011 | $0.00117 |
| Haiku 4.5 | $0.00005 | $0.00059 |
Grade A, and why
powerskills-desktop 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.
What it actually says
PowerSkills — Desktop
Desktop automation: screenshots, window management, keystrokes, app launching.
Requirements
- Windows with .NET Framework (System.Windows.Forms, System.Drawing)
Actions
.\powerskills.ps1 desktop <action> [--params]
| Action | Params | Description |
|---|---|---|
screenshot |
--out-file path.png [--window "title"] |
Full screen or window capture |
windows |
List all visible windows with title, PID, process name | |
focus |
--window "title" |
Bring window to foreground |
minimize |
--window "title" |
Minimize window |
maximize |
--window "title" |
Maximize window |
keys |
--keys "{ENTER}" [--window "title"] |
Send keystrokes (SendKeys syntax) |
launch |
--app notepad [--app-args "file.txt"] [--wait-ms 3000] |
Launch application |
Examples
# Full screen screenshot
.\powerskills.ps1 desktop screenshot --out-file screen.png
# Capture a specific window
.\powerskills.ps1 desktop screenshot --out-file outlook.png --window "Outlook"
# List all windows
.\powerskills.ps1 desktop windows
# Focus and type into Notepad
.\powerskills.ps1 desktop focus --window "Notepad"
.\powerskills.ps1 desktop keys --keys "Hello world{ENTER}" --window "Notepad"
# Launch an app
.\powerskills.ps1 desktop launch --app "notepad.exe" --app-args "C:\temp\notes.txt"
SendKeys Syntax
| Key | Syntax |
|---|---|
| Enter | {ENTER} |
| Tab | {TAB} |
| Escape | {ESC} |
| Ctrl+C | ^c |
| Alt+F4 | %{F4} |
| Shift+Tab | +{TAB} |
See Microsoft SendKeys docs for full syntax.
Output Fields
windows
title, pid, process, hwnd
screenshot
saved, width, height, window (if window capture)
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 75 lines · 53 tokens per session scan A 51f71b1a530a
powerskills-desktop is a skill published in the GitHub repository aloth/PowerSkills (47 stars, last pushed 1mo ago), licensed MIT. It adds 53 tokens to every session and 585 once invoked, about $0.0002 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 skills, from other repositories
opencli-autofix
Automatically fix broken OpenCLI adapters when commands fail. Load this skill when an opencli command fails — it guides you through collecting a trace artifact, patching the adapter, retrying, and filing an upstream GitHub issue after a verified fix. Works with any AI agent.
smart-search
A search-routing guide for OpenCLI, a command-line tool that lets coding agents search websites and other information sources. It helps choose a suitable source and check its current commands before searching.
opencli-adapter-author
Build or improve an OpenCLI JS adapter using observed site behavior, existing adapters and browser API evidence. For ad-hoc browser interaction, see opencli-browser.
opencli-browser
Drive Chrome with OpenCLI to inspect pages, interact with logged-in sites, capture API evidence, and manage native tabs, groups and windows. For reusable adapters, see opencli-adapter-author.
opencli-usage
Discover and invoke OpenCLI capabilities for websites and Chrome. Find commands, inspect schemas, interpret results and choose browser or adapter tools.
open-source
Documentation reference for writing Python code using the browser-use open-source library. Use this skill whenever the user needs help with Agent, Browser, or Tools configuration, is writing code that imports from browseruse, asks about @sandbox deployment, supported LLM models, Actor API, custom tools, lifecycle…