Open Agents is an open-source reference application for running background coding agents through a web interface, durable workflows, isolated Vercel sandboxes, and GitHub integration. Developers fork and adapt it to let agents make code changes without keeping a local computer running. The catalogue entries provide skills, agents, and instructions for its workflow.
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 vercel-labs/open-agents --skill deploy-open-harnessgit clone --depth 1 https://github.com/vercel-labs/open-agentsWrote 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/vercel-labs/open-agents/deploy-open-harness)<a href="https://agentmods.dev/skills/vercel-labs/open-agents/deploy-open-harness"><img src="https://agentmods.dev/badge/skills/vercel-labs/open-agents/deploy-open-harness/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/vercel-labs/open-agents/deploy-open-harness"><img src="https://agentmods.dev/badge/skills/vercel-labs/open-agents/deploy-open-harness.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 44 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00060 | $0.01629 |
| Opus 5.5 | $0.00024 | $0.00652 |
| Sonnet 5.5 | $0.00012 | $0.00326 |
| Haiku 4.5 | $0.00006 | $0.00163 |
Grade A, and why
deploy-open-harness 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 2mo 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 — 208 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are helping a user deploy their own copy of Open Harness.
Base your guidance on the current codebase, not on older Harness-era setup assumptions.
First rule: verify current requirements from the repo
Before giving deployment advice, read these files if you have not already:
README.mdapps/web/.env.exampleapps/web/lib/db/client.tsapps/web/lib/jwe/encrypt.tsapps/web/lib/crypto.tsapps/web/app/api/auth/signin/vercel/route.tsapps/web/app/api/auth/vercel/callback/route.tsapps/web/app/api/github/app/install/route.tsapps/web/app/api/github/app/callback/route.tsapps/web/lib/github/app-auth.tsapps/web/lib/redis.tsapps/web/lib/sandbox/config.ts
If the code and the docs disagree, trust the code and say so.
Do not rely on scripts/setup.sh.
Goals
Help the user:
- Decide whether they want a minimal deploy or the full GitHub-enabled coding-agent flow.
- Collect only the credentials actually required for that scope.
- Understand where to obtain each credential.
- Deploy this repo on Vercel.
- Complete first-run verification.
- Leave with a short next-steps checklist.
Safety rules
- Never ask the user to paste secrets into chat.
- Tell them where each value belongs, but keep secret values in Vercel project env vars or local env files.
- Separate blockers for a minimal deploy from blockers for the full GitHub-enabled flow.
- Be explicit when something is optional.
Scope the deployment first
Start by determining which path the user wants:
1) Minimal deploy
A working hosted app where the user can deploy it, sign in with Vercel, and use the product without GitHub repo access.
2) Full deploy
Everything in the minimal deploy, plus GitHub account linking, GitHub App installation, private repo access, pushes, and PR creation.
If the user is unsure, recommend minimal deploy first, then layer on GitHub.
Credential checklist
Use this checklist when guiding the user.
Required for the app to 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.
- 2mo ago First seen · 208 lines · 60 tokens per session scan A 0f010ea4c3bb
deploy-open-harness is a skill published in the GitHub repository vercel-labs/open-agents (5,882 stars, last pushed 2mo ago), licensed MIT. It adds 60 tokens to every session and 1,629 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-31.
deploy-open-harness compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| deploy-open-harnessvercel-labs/open-agents | Skill | 5.9k | 2mo ago | MIT | A | 60 | Claude Code, Codex |
| artifact-deploykirodotdev/KiroCrew | Skill | 4.8k | today | Apache-2.0 | A | 74 | Claude Code, Codex |
| remote-crew-microvmkirodotdev/KiroCrew | Skill | 4.8k | today | Apache-2.0 | A | 64 | Claude Code, Codex |
| capawesome-cloudcapawesome-team/skills | Skill | 54 | 2d ago | MIT | A | 172 | Claude Code, Codex |
| huggingface-jobsmetaspartan/cybara | Skill | 34 | yesterday | MIT | A | 36 | Claude Code, Codex |
| cloudflare-temporary-deploymetaspartan/cybara | Skill | 34 | yesterday | MIT | A | 24 | Claude Code, Codex |
| vigilante-issue-implementation-on-terraformaliengiraffe/vigilante | Skill | 41 | 3d ago | Apache-2.0 | A | 40 | Codex |