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-convexgit 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-convex)<a href="https://agentmods.dev/skills/triggerdotdev/trigger.dev/trigger-convex"><img src="https://agentmods.dev/badge/skills/triggerdotdev/trigger.dev/trigger-convex/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-convex"><img src="https://agentmods.dev/badge/skills/triggerdotdev/trigger.dev/trigger-convex.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00093 | $0.02989 |
| Opus 5.5 | $0.00037 | $0.01196 |
| Sonnet 5.5 | $0.00019 | $0.00598 |
| Haiku 4.5 | $0.00009 | $0.00299 |
Grade A, and why
trigger-convex 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 — 265 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Trigger.dev with Convex
Check the installed contract first
Locate @trigger.dev/convex/package.json, then read the adjacent README.md and
dist/client/index.d.ts. In a non-hoisted installation, resolve the package with:
node -p "require.resolve('@trigger.dev/convex/package.json')"
Use the installed declarations as authority. Older releases do not expose
refresh(). If it is absent, use durable polling or upgrade to a compatible
release; do not invent a replacement method or accept browser-supplied run state.
Keep the application's Convex version compatible with the package's peer dependency.
Do not pin an arbitrary preview URL unless the user explicitly needs that preview.
Choose the relevant flow:
| Request | Approach |
|---|---|
| Enqueue a report, render, import, or AI task | Call trigger.trigger inside the application's authenticated mutation. |
| Display durable status/results | Authorize the application's job, then call trigger.getRun from a query. |
| Update application records on completion | Register a short internal mutation using vRun. |
| Display responsive browser progress | Subscribe to Trigger Realtime; request an authorized Convex refresh on terminal events. |
| Restore an edit after reload or leaving the page | Persist the selected application job/request ID and inputs; recover owned work from Convex. |
| Recover paused status synchronization | Repair credentials/callback failures, then call authorized resume; do not enqueue another task. |
Install and configure
Install @trigger.dev/convex and convex. Deploy the actual task separately with
Trigger.dev; the component does not deploy task code. Keep TRIGGER_SECRET_KEY
only in the Convex server environment, for the intended Trigger environment.
// convex/convex.config.ts
import { defineApp } from "convex/server";
import triggerComponent from "@trigger.dev/convex/convex.config.js";
const app = defineApp();
app.use(triggerComponent);
export default app;
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 265 lines · 93 tokens per session scan A 4796095bc21e
trigger-convex is a skill published in the GitHub repository triggerdotdev/trigger.dev (16,667 stars, last pushed yesterday), licensed Apache-2.0. It adds 93 tokens to every session and 2,989 once invoked, about $0.0004 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-10-31.
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.
system-design-data-architecture
Design system data flows and data-layer ownership, consistency, and store choices from access patterns. Use for critical-flow design, DFD semantic review, data lineage, authority, replication, retention, or a data-tier bottleneck. Avoid unrelated framework stream/dataframe implementation questions.
webiny-api-opensearch-catalog
Name: createOpenSearchClient Import: import { createOpenSearchClient } from "webiny/api/opensearch" Source: @webiny/api-opensearch/client.ts.
cloud-native-serverless-orchestration
Use this skill when the user says 'step functions', 'state machine', 'amazon states language', 'asl', 'orchestrate lambdas', 'express workflow', 'distributed map', 'saga with step functions', 'workflow retries catch'. Designs AWS Step Functions state machines with correct ASL syntax, Retry/Catch error handling…