Trigger.dev is an open-source TypeScript platform for running long-lived AI workflows and background tasks. Developers use it for jobs and agents that need queues, retries, schedules, human approval, monitoring, or resources such as browsers and Python scripts. The catalogue entries provide instructions, skills, agents, and commands for working with this platform.
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 triggerdotdev/trigger.dev --skill trigger-getting-startedgit clone --depth 1 https://github.com/triggerdotdev/trigger.devWrote 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/triggerdotdev/trigger.dev/trigger-getting-started)<a href="https://agentmods.dev/skills/triggerdotdev/trigger.dev/trigger-getting-started"><img src="https://agentmods.dev/badge/skills/triggerdotdev/trigger.dev/trigger-getting-started/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/triggerdotdev/trigger.dev/trigger-getting-started"><img src="https://agentmods.dev/badge/skills/triggerdotdev/trigger.dev/trigger-getting-started.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 8 findings, 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 Privilege Escalation · line 135 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 135 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- medium MCP Rug Pull · line 32 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 43 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 58 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 60 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 142 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 180 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00142 | $0.02006 |
| Opus 5.5 | $0.00057 | $0.00802 |
| Sonnet 5.5 | $0.00028 | $0.00401 |
| Haiku 4.5 | $0.00014 | $0.00201 |
Grade A, and why
trigger-getting-started 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 16d 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 — 226 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Getting started with Trigger.dev
Set up Trigger.dev in an existing project. The end state is: the SDK installed, a
trigger.config.ts pointing at a project ref, a /trigger directory with at least
one exported task, and trigger dev running so the task shows up in the dashboard.
The fastest path is the CLI's own wizard, which performs every mechanical step below and also offers to install the MCP server and these agent skills:
npx trigger.dev@latest init
Prefer init when you can. Do the manual steps further down when init does not fit
(monorepos, an existing config to extend, or a non-interactive environment).
Authentication needs the human
The CLI can start account creation, but a person must verify their email and authorize access. In an agent session, start a resumable login instead of blocking on the CLI:
npx trigger.dev@latest login --email [email protected] --name "Alex Smith" --no-browser --no-wait
Give the printed URL to the user and ask them to complete sign-in and authorization. After they confirm, resume the saved authorization:
npx trigger.dev@latest login --no-browser
Do not create accounts or approve CLI access on the user's behalf. Once authenticated,
trigger init can create the first organization and project without a dashboard handoff.
A self-hosted instance may disable organization creation; if it does, ask the user to
create the organization in its dashboard first.
Manual setup
1. Authenticate (human authorization step)
For an interactive terminal:
npx trigger.dev@latest login
For an agent or headless terminal, use the resumable flow described above. Add
--api-url https://your-trigger-instance.com to both commands for self-hosting.
2. Install the packages
@trigger.dev/sdk is a runtime dependency; @trigger.dev/build is a dev dependency.
Pin both to the same version as the trigger.dev CLI you run; the CLI warns on a
mismatch during dev/deploy.
npm add @trigger.dev/sdk@latest
npm add --save-dev @trigger.dev/build@latest
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.
- 16d ago Changed · +9 lines dfb0343c1dde
- 1mo ago Changed · +2 lines abbe6e42741a
- 1mo ago First seen · 215 lines · 142 tokens per session scan A 2de9150ee978
trigger-getting-started is a skill published in the GitHub repository triggerdotdev/trigger.dev (16,549 stars, last pushed today), licensed Apache-2.0. It adds 142 tokens to every session and 2,006 once invoked, about $0.0006 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-30.
Other skills, from other repositories
workflow
Creates durable, resumable workflows using Vercel's Workflow SDK. Use when building workflows that need to survive restarts, pause for external events, retry on failure, or coordinate multi-step operations over time. Triggers on mentions of "workflow", "durable functions", "resumable", "workflow sdk", "queue"…
migrating-world-v4-to-v5
Upgrades a custom Workflow SDK World implementation from the v4 spec to v5. Use when a package implements the World interface from @workflow/world and is moving to 5.x — event IDs that are ULIDs rather than slot positions, Event id is not slot-numbered at replay time, a specVersion the runtime refuses, writeToStream /…
migrating-workflow-v4-to-v5
Upgrades an app from Workflow SDK 4.x to 5.0. Use when bumping the workflow / @workflow/ dependencies to v5, or when hitting removed v4 APIs — runStep, stepEntrypoint, workflow/internal/private, @workflow/core/private, writeToStream / closeStream / readFromStream on a World, world.steps.get without a runId…
migrating-to-workflow-sdk
Migrates Temporal, Inngest, Trigger.dev, and AWS Step Functions workflows to the Workflow SDK. Use when porting Activities, Workers, Signals, step.run(), step.waitForEvent(), Trigger.dev tasks / wait.forToken / triggerAndWait, ASL JSON state machines, Task/Choice/Wait/Parallel states, task tokens, or child workflows.
workflow-init
Install and configure Vercel Workflow SDK before it exists in nodemodules. Use when the user asks to "install workflow", "set up workflow", "add durable workflows", "configure workflow sdk", or "init workflow" for Next.js, Express, Hono, Fastify, NestJS, Nitro, Nuxt, Astro, SvelteKit, or Vite.
internal-dev-workbench
Spin up a portless + tmux dev session for the Workflow SDK that gives each git worktree isolated . .localhost URLs for the Next.js workbench and the observability UI, plus a Claude statusline that surfaces those URLs. Use only when the user asks for a "portless dev session", a "tmux dev layout for workflow"…