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 instructions/vercel/workflow/agents-mdgit clone --depth 1 https://github.com/vercel/workflowWhat 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 | $0.08698 | $0.08698 |
| Opus 5 | $0.04349 | $0.04349 |
| Sonnet 5 | $0.01740 | $0.01740 |
| Haiku 4.5 | $0.00870 | $0.00870 |
Grade A, and why
workflow AGENTS.md 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 yesterday.
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 — 543 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent instructions
CRITICAL RULES:
- NEVER push directly to the
mainorstablebranches - Do not remove or break agent-discoverable docs sitemap behavior: keep docs/app/sitemap.md/route.ts and docs/app/[lang]/sitemap.md/route.ts, and keep the sitemap link in docs/app/[lang]/llms.mdx/[[...slug]]/route.ts.
Overview
Workflow SDK is a durable functions framework for JavaScript/TypeScript that enables writing long-running, stateful application logic on top of stateless compute. The runtime persists progress as an event log and deterministically replays code to reconstruct state after cold starts, failures, or scale events.
This repository contains the client-side SDK code for workflows, along with example apps that showcase Workflow SDK in action.
Architecture
Core components
- packages/core: Core workflow runtime and primitives (
@workflow/core) - packages/next: Next.js integration (
@workflow/next) - packages/cli: Command-line interface (
@workflow/cli) - packages/world: Core interfaces and types for workflow storage backends (
@workflow/world) - packages/world-local: Filesystem-based workflow backend for local development and testing (
@workflow/world-local) - packages/world-vercel: Production workflow backend for Vercel platform deployments (
@workflow/world-vercel) - packages/swc-plugin-workflow: SWC compiler plugin for workflow transformations
- workbench/example: Basic workflow examples using the CLI (aka "standalone mode")
- workbench/nextjs-turbopack: Workflow examples using the Next.js integration
Workflow execution model
Workflows consist of two types of functions:
- Workflow functions (
"use workflow"): Orchestrators that run in a sandboxed VM without full Node.js access - Step functions (
"use step"): Individual pieces of logic with full Node.js runtime access
The framework uses compiler transformations to split workflow files into separate bundles for client, workflow, and step execution contexts.
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.
- yesterday First seen · 543 lines · 8,698 tokens per session scan A f6fabb8c5999
workflow AGENTS.md is an instructions file published in the GitHub repository vercel/workflow (2,363 stars, last pushed 3d ago), licensed Apache-2.0. It adds 8,698 tokens to every session, about $0.0435 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-30.
Other instructions, from other repositories
trigger.dev AGENTS.md
Instructions for triggerdotdev/trigger.dev, covering agents.md, build and development commands, build packages (required before running), verifying changes and apps and internal packages — use typecheck.
trigger.dev copilot-instructions.md
Instructions for triggerdotdev/trigger.dev: This is the repo for Trigger.dev, a background jobs platform written in TypeScript. Our webapp at apps/webapp is a Remix 2.1 app that uses Node.js v20. Our SDK is an isomorphic TypeScript SDK at packages/trigger-sdk. Always prefer using isomorphic code like fetch…
trigger.dev CLAUDE.md
Instructions for triggerdotdev/trigger.dev, a project described as: Trigger.dev – build and deploy fully‑managed AI agents and workflows.
appwrite AGENTS.md
Instructions for appwrite/appwrite, covering appwrite, commands, stack, layout and libraries.
1flowbase AGENTS.md
Instructions for taichuy/1flowbase, covering 记忆, 用户偏好, 本项目相关skill在, 本项目 skills and 质量控制.
decapod CLAUDE.md
Instructions for DecapodLabs/decapod, covering claude.md - agent entrypoint, orientation & documentation, mandatory prompt safety gate, project context and quick start.