agentmods.dev

workflow-deployment

A procedure for testing and deploying workflow changes with a real example app. It covers building the app, deploying it to Vercel, sending test requests, and inspecting the results.

In plain words
What is it for?
Use it to build the example, create a Vercel preview deployment, trigger named workflows with arguments, and inspect their output.
Why use it?
It gives developers a consistent path from code changes to a deployed workflow test, making it easier to verify that the change works outside the local project.

Cursor rule for Cursor

2.4k 4d ago A scan 6 tokens original Apache-2.0
View the source file vercel/workflow
Install

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.

agentmods
npx agentmods add rules/vercel/workflow/workflow-deployment
Clone the repo
git clone --depth 1 https://github.com/vercel/workflow

Made for: Cursor.

Per session 6 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 446 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00006 $0.00446
Opus 5 $0.00003 $0.00223
Sonnet 5 $0.00001 $0.00089
Haiku 4.5 $0.00001 $0.00045

Measured 2d ago against content hash b1f11ae5b524, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

workflow-deployment scanned grade A with 1 finding 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 2d 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -X POST "https://w-abcdefg1234-uncurated-tests.vercel.app/api/trigger\?workflow=simple&args\=42"
.cursor/rules/workflow-deployment.mdc · 54 lines

What it actually says

Workflow Testing and Deployment Process

When testing and deploying changes in workflow, follow these steps to see them work with a real example app:

Deployment Steps

  1. Make your changes to the codebase

  2. Build the project

    cd workbench/example
pnpx turbo build

  3. Deploy to Vercel

    cd workbench/example
vc deploy --prebuilt

  4. Test the deployment Make a POST request to the "Preview" URL logged from the deployment command:

    curl -X POST "https://w-abcdefg1234-uncurated-tests.vercel.app/api/trigger\?workflow=simple&args\=42"

    (Replace the URL with the actual preview URL from your deployment) (If a different workflow/argument needs to be tested, adjust the URL accordingly. The URL takes a workflow and and args query param. The workflows can be found inside workbench/example/workflows - the exported workflow function name is the name of the workflow, and the args are a comma separated list of inputs to that function)

    Here's an example of testing the AI workflow

    curl -X POST "https://w-abcdefg1234-uncurated-tests.vercel.app/api/trigger\?workflow=ai&args\=what+is+love?"

  5. Inspect the results Open the "Inspect" URL in a browser (logged from the previous CLI command) Attempt to open the URL using the open CLI tool. If it's not installed, just provide the link to the user to allow them to open it.

Important Notes

  • All build and deploy commands should be run from the workbench/example directory
  • The preview URL will be different for each deployment
  • The inspect URL allows you to monitor the workflow execution
  • Make sure to use the actual URLs provided by the deployment output, not the example URLs shown above
Changes

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.

  1. 2d ago First seen · 54 lines · 6 tokens per session scan A b1f11ae5b524

Subscribe to this mod's changes

workflow-deployment is a cursor rule published in the GitHub repository vercel/workflow (2,363 stars, last pushed 4d ago), licensed Apache-2.0. It adds 6 tokens to every session and 446 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

DevOps and cloudOrchestrationProductivityTestingai-agentsdurable-executionserverlessvercelworkflow-engine
Related

Other cursor rules, from other repositories

writing-tasks

Guidelines for writing Trigger.dev tasks.

triggerdotdev/trigger.dev · 7,920 tokens

otel-metrics

Guidelines for creating OpenTelemetry metrics to avoid cardinality issues.

triggerdotdev/trigger.dev · 0 tokens

executing-commands

how to run commands in the monorepo.

triggerdotdev/trigger.dev · 154 tokens

webapp

Making updates to the main trigger.dev remix webapp.

triggerdotdev/trigger.dev · 0 tokens

migrations

how to create and apply database migrations.

triggerdotdev/trigger.dev · 7 tokens

repo

understanding the structure of the monorepo.

triggerdotdev/trigger.dev · 47 tokens