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 skills/openhands/extensions/openhands-automationnpx skills add OpenHands/extensions --skill openhands-automationgit clone --depth 1 https://github.com/OpenHands/extensionsWrote 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/openhands/extensions/openhands-automation)<a href="https://agentmods.dev/skills/openhands/extensions/openhands-automation"><img src="https://agentmods.dev/badge/skills/openhands/extensions/openhands-automation.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.00062 | $0.10058 |
| Opus 5 | $0.00031 | $0.05029 |
| Sonnet 5 | $0.00012 | $0.02012 |
| Haiku 4.5 | $0.00006 | $0.01006 |
Grade A, and why
openhands-automation scanned grade A with 1 finding 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 2d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
Windows PowerShell equivalents for the automation API `curl` examples and shell-variable conventions are in `references/windows.md`. How it starts
The opening of the file, as written. The whole thing — 890 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenHands Automations
Create and manage automations that run inside an OpenHands agent server — triggered by cron schedules or webhook events (GitHub, custom services).
Windows PowerShell equivalents for the automation API curl examples and shell-variable conventions are in references/windows.md.
Automation Creation Process
The agent must follow these steps when creating an automation:
- Quickly check that you can access the correct automations backend using the auth mechanism below
- Quickly check that you can access any necessary integrations (e.g. GitHub, Slack); if access fails, inform the user and stop
- Ask the user for any necessary information, e.g. if you need the name of a Slack channel or GitHub repo to proceed
- Write the code or prompt that will be sent to the automations backend inside the current workspace
- Show the code to the user with the
canvas_uitool if available, otherwise present it in a fenced code block in your reply - Message the user with a concise summary of how the automation will behave, and ask if they are ready to deploy it
Architecture
Two components work together to run automations:
Automation Service (API at OPENHANDS_HOST/api/automation/v1)
Manages the when: holds automation definitions, schedules cron-triggered runs, dispatches webhook-triggered runs, and receives completion callbacks to mark runs as done. This is the API you call to create, update, and manage automations.
Agent Server (accessible as AGENT_SERVER_URL inside script runs)
Manages the what: the runtime environment where automation scripts execute and where conversations (AI agent interactions with tools, bash, file editing, etc.) run. When a run is triggered, the automation service uploads the automation's tarball to the agent server, which unpacks and runs the entrypoint script. The script connects back to the agent server using AGENT_SERVER_URL and a session API key to start, monitor, and stop conversations.
The agent server typically runs inside a sandbox (a Docker or Kubernetes container). Some deployments use sandboxless mode, where the agent server runs directly on a host.
What ships with it
9 files 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.
- 2d ago First seen · 890 lines · 62 tokens per session scan A a5e12729ebfe
openhands-automation is a skill published in the GitHub repository OpenHands/extensions (143 stars, last pushed yesterday), licensed MIT. It adds 62 tokens to every session and 10,058 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for disaster recovery setup or full cluster backups (use gke-backup-dr instead).
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running cluster security audits (auditcluster.sh), configuring Workload Identity Federation (impersonation, KSA/GSA binding, and pod setup), enforcing Network Policies (default-deny…
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
cloud-architect
Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure, and GCP. Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments. Invoke for Well-Architected Framework, cost…