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 remove-demo-limitsgit 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/remove-demo-limits)<a href="https://agentmods.dev/skills/vercel-labs/open-agents/remove-demo-limits"><img src="https://agentmods.dev/badge/skills/vercel-labs/open-agents/remove-demo-limits.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
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 →
- high Rogue Agent · line 36 Skill modifies its own code, configuration, or behavior at runtime. Self-modification enables an agent to escalate privileges, disable safety constraints, or install persistent backdoors.Fix: Prevent the skill from modifying its own code, SKILL.md, or configuration files. Treat skill files as read-only at runtime.
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.00073 | $0.00518 |
| Opus 5 | $0.00036 | $0.00259 |
| Sonnet 5 | $0.00015 | $0.00104 |
| Haiku 4.5 | $0.00007 | $0.00052 |
Grade A, and why
remove-demo-limits 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 7d 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
Remove the managed-template trial restrictions with the smallest coherent change.
Goal
Make the fork behave like a normal self-hosted deployment:
- no trial session cap
- no trial message cap
- no hosted-only restriction errors
- no hosted-demo delete restrictions
- no dead helper code or stale tests
Inspect first
Read these files before editing:
apps/web/lib/managed-template-trial.tsapps/web/app/api/sessions/route.tsapps/web/app/api/chat/route.tsapps/web/app/api/sessions/[sessionId]/chats/[chatId]/messages/[messageId]/route.tsapps/web/app/api/sessions/route.test.tsapps/web/app/api/chat/route.test.tsapps/web/app/api/sessions/[sessionId]/chats/[chatId]/messages/[messageId]/route.test.ts
Then search for these identifiers and strings to catch older or newer variants:
isManagedTemplateTrialUserMANAGED_TEMPLATE_TRIAL_deploy-your-ownopen-agents.devvercel.comThis hosted deployment includesdoes not allow message deletion
Required changes
- Remove the guards that block session creation, chat messages, or message deletion for managed-template users.
- If the auth callback still blocks non-Vercel emails on hosted deployments, remove that restriction too.
- Delete
apps/web/lib/managed-template-trial.tsif it becomes unused; otherwise simplify it so no dead exports remain. - Remove or update tests that assert the hosted caps, delete restrictions, or hosted-only auth gating.
- Do not add feature flags, env toggles, or new dependencies. Prefer deleting the restriction code outright.
- Keep unrelated auth, session ownership, and sandbox behavior unchanged.
Verification
This repo uses Bun. After the edits:
- run
bun run ci - if a failure is pre-existing, say that clearly and separate it from your changes
Output
Report:
- which restrictions were removed
- which files changed
- verification result
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.
- 7d ago First seen · 53 lines · 73 tokens per session scan A 6126746a39a0
remove-demo-limits is a skill published in the GitHub repository vercel-labs/open-agents (5,807 stars, last pushed 9d ago), licensed MIT. It adds 73 tokens to every session and 518 once invoked, about $0.0004 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-31.
Other skills, from other repositories
adk-unit-design
Writes an as-built architecture document for one ADK code unit — purpose, execution flow, data flow, cross-class dependencies, extension points, and the parts that must not change — to docs/design/{topic}/{unit}/index.md. It describes the code as implemented, not a proposed design, and its reader is a developer about…
artifact-deploy
One-click deploy a user's pre-built app/artifact into their OWN AWS account and get a global public HTTPS link (Vercel-like), with a default TTL and promote-to-persistent. Use when the user says "deploy this", "ship this demo", "give me a public link", "share this externally", or "deploy to AWS".
widgets
Render rich HTML inline via tags with theme-aware styling. Load when emitting an mcwidget so the iframe inherits the dashboard theme instead of clashing with light / dark / custom palettes.
explain-for
Explain a topic, a piece of code, an error, or a design decision calibrated to one named audience — a 5-year-old, a 5th grader, a manager, a designer, a graduate student, a parent. Resolves who the explanation is for (from the request, or from what memory already records about that person), establishes the ground…
web-verify
Look at your OWN front-end change before claiming it works -- navigate the loopback URL of a dev server or pod you started, screenshot the surface you changed, read the image to judge it, and embed it in chat. Three capture backends: playwright-cli (the session the dashboard Browser panel shows), the agent-browser CLI…
learn-from-sage
Detection-gap (miss) analysis for Code Review Sage. Learn from shipped fixes, acted-on human comments, and design outcomes to close reviewer blind spots. Inline during review stages a candidate; a human triggers a one-shot AI consolidation into the live ruleset.