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 zeenie-ai/OpenCompany --skill screen-control-skillgit clone --depth 1 https://github.com/zeenie-ai/OpenCompanyWrote 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/zeenie-ai/opencompany/screen-control-skill)<a href="https://agentmods.dev/skills/zeenie-ai/opencompany/screen-control-skill"><img src="https://agentmods.dev/badge/skills/zeenie-ai/opencompany/screen-control-skill/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/zeenie-ai/opencompany/screen-control-skill"><img src="https://agentmods.dev/badge/skills/zeenie-ai/opencompany/screen-control-skill.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00025 | $0.00848 |
| Opus 5 | $0.00013 | $0.00424 |
| Sonnet 5 | $0.00005 | $0.00170 |
| Haiku 4.5 | $0.00003 | $0.00085 |
Grade A, and why
screen-control-skill 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 12d 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 — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Screen Control Tool
Control screen settings on Android device.
How It Works
This skill provides instructions for the Screen Control Automation tool node. Connect the Screen Control Automation node to Zeenie's input-tools handle to enable screen control.
screen_control Tool
Control screen brightness and display settings.
Schema Fields
| Field | Type | Required | Description |
|---|---|---|---|
| action | string | Yes | Action to perform (see below) |
| parameters | object | No | Additional parameters for set actions |
Actions
| Action | Description |
|---|---|
status |
Get current screen settings |
set_brightness |
Set screen brightness level |
wake |
Wake the screen |
auto_brightness_on |
Enable auto-brightness |
auto_brightness_off |
Disable auto-brightness |
Examples
Get screen status:
{
"action": "status"
}
Set brightness to 50%:
{
"action": "set_brightness",
"parameters": {
"level": 50
}
}
Wake the screen:
{
"action": "wake"
}
Enable auto-brightness:
{
"action": "auto_brightness_on"
}
Disable auto-brightness:
{
"action": "auto_brightness_off"
}
Response Formats
Status response:
{
"success": true,
"service": "screen_control",
"action": "status",
"data": {
"brightness": 75,
"auto_brightness": true,
"screen_on": true,
"screen_timeout": 30000
}
}
Set brightness response:
{
"success": true,
"service": "screen_control",
"action": "set_brightness",
"data": {
"previous_brightness": 100,
"new_brightness": 50
}
}
Response Fields
| Field | Type | Description |
|---|---|---|
| brightness | int | Current brightness (0-100) |
| auto_brightness | boolean | Auto-brightness enabled |
| screen_on | boolean | Screen is currently on |
| screen_timeout | int | Timeout in milliseconds |
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.
- 12d ago First seen · 164 lines · 25 tokens per session scan A 9b24792f7288
screen-control-skill is a skill published in the GitHub repository zeenie-ai/OpenCompany (883 stars, last pushed today), licensed MIT. It adds 25 tokens to every session and 848 once invoked, about $0.0001 per session on Opus 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
node-connect
Diagnose OpenClaw Control UI browser and native Android, iOS, or macOS node connection failures across route, auth, pairing, QR/setup-code, and reconnect states.
browser-automation
Use when controlling web pages with the OpenClaw browser tool, especially multi-step flows, login checks, tab management, or recovery from stale refs/timeouts.
imsg
Use the imsg CLI from OpenClaw agents for iMessage/SMS DMs, groups, replies, reactions, polls, watching, and private-API actions.
coding-agent
Delegate coding work to Codex, Claude Code, or OpenCode as background workers; not simple edits or read-only code lookup.
acp-router
Route plain-language requests for Claude Code, Cursor, Copilot, OpenClaw ACP, OpenCode, Gemini CLI, Qwen, Kiro, Kimi, iFlow, Factory Droid, Kilocode, or explicit ACP harness work into either OpenClaw ACP runtime sessions or direct acpx-driven sessions ("telephone game" flow). For coding-agent thread requests, read…
control-ui
Operate and troubleshoot the OpenClaw Control UI: navigate connected clients, organize sessions, build session dashboards, and handle direct or Tailscale-hosted Gateways.