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 vertex-agent-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/vertex-agent-skill)<a href="https://agentmods.dev/skills/zeenie-ai/opencompany/vertex-agent-skill"><img src="https://agentmods.dev/badge/skills/zeenie-ai/opencompany/vertex-agent-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/vertex-agent-skill"><img src="https://agentmods.dev/badge/skills/zeenie-ai/opencompany/vertex-agent-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.00061 | $0.00494 |
| Opus 5 | $0.00030 | $0.00247 |
| Sonnet 5 | $0.00012 | $0.00099 |
| Haiku 4.5 | $0.00006 | $0.00049 |
Grade A, and why
vertex-agent-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 9d 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
Vertex Managed Agent Skill
Delegate work to Google's managed agent (the Antigravity harness on the Gemini Enterprise Agent Platform). The agent runs entirely in Google's cloud inside an isolated Linux sandbox with Python 3.11, Node.js, bash, file management, Google Search, and URL fetching.
Tool: delegate_to_vertex_managed_agent
Non-blocking delegation. Two fields:
| Field | Purpose |
|---|---|
task |
What the cloud agent should accomplish — its system instruction for the run |
context |
Optional background, inputs, or data the agent needs |
The call returns immediately with {"status": "delegated", "task_id": ...}.
Use check_delegated_tasks to poll for the result — do NOT re-delegate
the same task while one is in flight.
When to delegate to the cloud agent
- Multi-step research: search the web, fetch pages, synthesize a report.
- Compute jobs: run Python/Node code, process data, generate files — all inside the cloud sandbox, not on this machine.
- Long-running work you want isolated from the local workflow.
Prefer LOCAL tools (python_executor, shell, file tools) when the work
needs files in this workflow's workspace — the cloud sandbox cannot see
local files unless their content is passed in context.
Behavior notes
- The cloud agent keeps its own multi-turn state: when a simpleMemory node is connected to the Vertex Agent, conversation and sandbox (installed packages, created files) persist across runs for up to 7 days.
- Cloud-side tool usage (sandbox commands, searches) appears on the canvas as Cloud Tool nodes wired to the Vertex Agent — they are display-only indicators, safe to delete.
- Task descriptions should be self-contained: the cloud agent cannot ask you follow-up questions mid-run.
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.
- 9d ago First seen · 54 lines · 61 tokens per session scan A a123d62cd569
vertex-agent-skill is a skill published in the GitHub repository zeenie-ai/OpenCompany (883 stars, last pushed yesterday), licensed MIT. It adds 61 tokens to every session and 494 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
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.
gh-issues
Fetch GitHub issues, select candidates, spawn background fix agents, open PRs, and optionally process PR review comments.