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 chat-sdkgit 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/chat-sdk)<a href="https://agentmods.dev/skills/vercel-labs/open-agents/chat-sdk"><img src="https://agentmods.dev/badge/skills/vercel-labs/open-agents/chat-sdk/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/chat-sdk"><img src="https://agentmods.dev/badge/skills/vercel-labs/open-agents/chat-sdk.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.00191 | $0.02215 |
| Opus 5.5 | $0.00076 | $0.00886 |
| Sonnet 5.5 | $0.00038 | $0.00443 |
| Haiku 4.5 | $0.00019 | $0.00221 |
Grade A, and why
chat-sdk 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 1mo 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 — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chat SDK
Unified TypeScript SDK for building chat bots across Slack, Teams, Google Chat, Discord, Telegram, GitHub, Linear, and WhatsApp. Write bot logic once, deploy everywhere.
Start with published sources
When Chat SDK is installed in a user project, inspect the published files that ship in node_modules:
node_modules/chat/docs/ # bundled docs
node_modules/chat/dist/index.d.ts # core API types
node_modules/chat/dist/jsx-runtime.d.ts # JSX runtime types
node_modules/chat/docs/contributing/ # adapter-authoring docs
node_modules/chat/docs/guides/ # framework/platform guides
If one of the paths below does not exist, that package is not installed in the project yet.
Read these before writing code:
node_modules/chat/docs/getting-started.mdx— install and setupnode_modules/chat/docs/usage.mdx—Chatconfig and lifecyclenode_modules/chat/docs/handling-events.mdx— event routing and handlersnode_modules/chat/docs/threads-messages-channels.mdx— thread/channel/message modelnode_modules/chat/docs/posting-messages.mdx— post, edit, delete, schedulenode_modules/chat/docs/streaming.mdx— AI SDK integration and streaming semanticsnode_modules/chat/docs/cards.mdx— JSX cardsnode_modules/chat/docs/actions.mdx— button/select interactionsnode_modules/chat/docs/modals.mdx— modal submit/close flowsnode_modules/chat/docs/slash-commands.mdx— slash command routingnode_modules/chat/docs/direct-messages.mdx— DM behavior andopenDM()node_modules/chat/docs/files.mdx— attachments/uploadsnode_modules/chat/docs/state.mdx— persistence, locking, dedupenode_modules/chat/docs/adapters.mdx— cross-platform feature matrixnode_modules/chat/docs/api/chat.mdx— exactChatAPInode_modules/chat/docs/api/thread.mdx— exactThreadAPInode_modules/chat/docs/api/message.mdx— exactMessageAPInode_modules/chat/docs/api/modals.mdx— modal element and event details
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.
- 1mo ago First seen · 210 lines · 191 tokens per session scan A d6d1224c2d01
chat-sdk is a skill published in the GitHub repository vercel-labs/open-agents (5,852 stars, last pushed 1mo ago), licensed MIT. It adds 191 tokens to every session and 2,215 once invoked, about $0.0008 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.
Other skills, from other repositories
azure-identity-ts
Authenticate to Azure services using Azure Identity library for JavaScript (@azure/identity). Use when configuring authentication with DefaultAzureCredential, managed identity, service principals, or interactive browser login.
zod-validation-utilities
Creates reusable Zod v4 schemas, validates API payloads, forms, and configuration input, transforms and coerces data safely, and handles validation errors with strong type inference for TypeScript applications. Use when designing validation layers, parsing z.string(), z.object(), or z.email() schemas, or implementing…
capacitor-plugin-development
Guides the agent through creating and maintaining Capacitor plugins from scratch. Covers scaffolding a new plugin project, designing the TypeScript API, implementing native iOS (Swift) and Android (Java/Kotlin) bridges, implementing the web layer, defining TypeScript type definitions, plugin configuration values…
aidd-error-causes
Use the error-causes library for structured error handling in JavaScript/TypeScript. Use when throwing errors, catching errors, defining error types, or implementing error routing.
aidd-namespace
Ensures types and related functions are authored and consumed in a modular, discoverable, tree-shakeable pattern. Use when creating types, refactoring type folders, defining schemas, importing types, or when the user mentions type namespaces, constants, or Schema.ToType.
aidd-javascript-io-effects
Isolate network I/O and side effects using the saga pattern with call and put. Use when making network requests, invoking side effects, or implementing Redux sagas.