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-authoring-tasksgit 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-authoring-tasks)<a href="https://agentmods.dev/skills/triggerdotdev/trigger.dev/trigger-authoring-tasks"><img src="https://agentmods.dev/badge/skills/triggerdotdev/trigger.dev/trigger-authoring-tasks/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-authoring-tasks"><img src="https://agentmods.dev/badge/skills/triggerdotdev/trigger.dev/trigger-authoring-tasks.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
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 →
- medium Agent Snooping · line 18 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00115 | $0.00954 |
| Opus 5.5 | $0.00046 | $0.00382 |
| Sonnet 5.5 | $0.00023 | $0.00191 |
| Haiku 4.5 | $0.00012 | $0.00095 |
Grade A, and why
trigger-authoring-tasks 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Authoring Trigger.dev Tasks
The full, version-pinned reference for authoring tasks ships inside your installed @trigger.dev/sdk. Read it before writing code — it always matches the SDK version in this project, so it never drifts:
- Skill:
node_modules/@trigger.dev/sdk/skills/trigger-authoring-tasks/SKILL.md— the complete guide (setup,schemaTask, retries, triggering + the Result shape, idempotency, waits, metadata, scheduled tasks, queues/concurrency,trigger.config.ts). - Docs: the full, version-pinned docs ship bundled at
node_modules/@trigger.dev/sdk/docs/; the skill above lists the exact pages it draws from in itssources:frontmatter. Grep for an API, e.g.grep -rl "schemaTask" node_modules/@trigger.dev/sdk/docs/.
If those paths don't exist, @trigger.dev/sdk isn't installed yet — install it first. In a non-hoisted layout, resolve the package with node -p "require.resolve('@trigger.dev/sdk/package.json')" and read skills/ + docs/ beside it.
Always import from @trigger.dev/sdk — never @trigger.dev/sdk/v3 (deprecated alias) or @trigger.dev/core.
Common mistakes
-
CRITICAL: Treating the wait result as the output.
triggerAndWaitandwait.forTokenreturn a Result object, not the raw output.- Wrong:
const out = await childTask.triggerAndWait(p); use(out.foo); - Correct:
const r = await childTask.triggerAndWait(p); if (r.ok) use(r.output.foo);(or.unwrap()).
- Wrong:
-
Wrapping
triggerAndWait/batchTriggerAndWait/waitinPromise.all.- Wrong:
await Promise.all([childTask.triggerAndWait(a), childTask.triggerAndWait(b)]); - Correct:
await childTask.batchTriggerAndWait([{ payload: a }, { payload: b }]);(or a sequential for-loop).
- Wrong:
-
Importing the task instance into backend code.
- Wrong:
import { emailSequence } from "~/trigger/emails";in a route handler. - Correct:
import type { emailSequence }plustasks.trigger<typeof emailSequence>("email-sequence", payload).
- Wrong:
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 · 58 lines · 115 tokens per session scan A 33f2427c5f39
trigger-authoring-tasks is a skill published in the GitHub repository triggerdotdev/trigger.dev (16,592 stars, last pushed today), licensed Apache-2.0. It adds 115 tokens to every session and 954 once invoked, about $0.0005 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-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.
nextjs-app-router
Full end-to-end tRPC setup for Next.js App Router. Covers route handler with fetchRequestHandler (GET + POST exports), TRPCProvider with QueryClientProvider, createTRPCOptionsProxy for RSC prefetching, HydrateClient/HydrationBoundary for hydration, useSuspenseQuery for Suspense, and server-side callers.
nextjs-pages-router
Set up tRPC in Next.js Pages Router with createNextApiHandler, createTRPCNext, withTRPC HOC, SSR via ssr option and ssrPrepass, SSG via createServerSideHelpers with getStaticProps, and server-side helpers for getServerSideProps prefetching.
subscriptions
Set up real-time event streams with async generator subscriptions using .subscription(async function() { yield }). SSE via httpSubscriptionLink is recommended over WebSocket. Use tracked(id, data) from @trpc/server for reconnection recovery with lastEventId. WebSocket via wsLink and createWSClient from @trpc/client…