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 CodeInfinity1/Stram --skill desktop-ui-controlgit clone --depth 1 https://github.com/CodeInfinity1/StramWrote 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/codeinfinity1/stram/desktop-ui-control)<a href="https://agentmods.dev/skills/codeinfinity1/stram/desktop-ui-control"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/desktop-ui-control/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/codeinfinity1/stram/desktop-ui-control"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/desktop-ui-control.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.00034 | $0.00479 |
| Opus 5.5 | $0.00014 | $0.00192 |
| Sonnet 5.5 | $0.00007 | $0.00096 |
| Haiku 4.5 | $0.00003 | $0.00048 |
Grade A, and why
desktop-ui-control 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.
How it starts
The opening of the file, as written. The whole thing — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Desktop UI Control
Purpose
Control Windows applications safely using native Stram OS tools. The assistant should observe windows and UI Automation elements before acting, then verify after each action.
When To Use
Use for Windows app workflows, app dialogs, settings panels, installer prompts, local desktop tasks, and native UI troubleshooting.
Inputs And Evidence
- User goal, target app/window, allowed actions, and expected final state.
os_windowsoutput, UIA selector map, element IDs, active window metadata, screenshots.- Approval status for UI observation and state-changing actions.
Tool Map
active_windowos_windowsos_observe_uios_click_elementos_type_textos_send_keysos_scroll_elementos_switch_windowos_window_state
Workflow
- List windows or inspect active window.
- Observe UIA tree with approval when element actions are needed.
- Choose targets from observed element IDs, not guessed coordinates.
- Perform one action at a time.
- Observe again and compare against expected state.
- Stop for credentials, destructive prompts, ambiguity, or repeated failed actions.
Native Implementation Boundaries
- Use Stram
os_*tools only. - Do not import Windows-use, Claude computer, OpenAI computer-use, or external reference code as implementation.
- Upstream projects are reference evidence for safe loop design only.
Safety And Approval
- UI observation and mutating actions are approval-gated because screens may contain private data.
- Do not type secrets unless the user provides them for that exact workflow.
- Destructive app actions require explicit confirmation.
Verification
- Verify active window and UI state after every action.
- Prefer element actions over coordinates.
- Use screenshots only when needed and store/delete them through native screen tools.
Failure Modes
- Clicking stale element IDs.
- Typing into the wrong app.
- Continuing after a permission or payment dialog appears.
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 · 71 lines · 34 tokens per session scan A 4c907f2dae5a
desktop-ui-control is a skill published in the GitHub repository CodeInfinity1/Stram (11 stars, last pushed 2mo ago), licensed MIT. It adds 34 tokens to every session and 479 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-09-03.
Other skills, from other repositories
ask-agents
Send a task or question to Claude Code and/or Gemini as external subagents and report back what they said. Use when the user asks to ask Claude, ask Gemini, ask both, get a second opinion, split reviewer roles, or compare external agents.
review-plan
Review a proposed plan with a single-pass structured critique and a clear verdict. Use when the user asks to review a plan, stress-test a plan, critique a workflow, identify risks, or improve an execution sequence.
alive:settings
The human wants to adjust how the system behaves — not what it contains, but how it feels. Voice, rhythm, preferences, walnut-level config, full permissions toggleable, named squirrel config, action logging toggle. The system adapting to them. Routes to preferences.yaml or walnut config.yaml depending on scope. For…
lark-contact
A Feishu (Lark) contacts tool for finding users or bots and looking up their profiles and contact details.
oci-services-expert
Expert guidance on Oracle Cloud Infrastructure services, architecture patterns, cost optimization, and deployment strategies. Use when designing on OCI, selecting OCI services, estimating cost, or applying OCI enterprise best practices.
openai-agentkit
Build production multi-agent systems with OpenAI AgentKit and the Agents SDK — orchestration, handoffs, and routines. Use when writing agents against OpenAI's AgentKit/Agents SDK or porting an agent design to the OpenAI stack.