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.
Borrowing it
Nothing to install: this file belongs to triggerdotdev/trigger.dev. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/triggerdotdev/trigger.dev/main/.claude/skills/drizzle/SKILL.mdgit 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/drizzle)<a href="https://agentmods.dev/skills/triggerdotdev/trigger.dev/drizzle"><img src="https://agentmods.dev/badge/skills/triggerdotdev/trigger.dev/drizzle/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/drizzle"><img src="https://agentmods.dev/badge/skills/triggerdotdev/trigger.dev/drizzle.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Snyk pass
- NVIDIA SkillSpector pass
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.00000 | $0.02807 |
| Opus 5.5 | $0.00000 | $0.01123 |
| Sonnet 5.5 | $0.00000 | $0.00561 |
| Haiku 4.5 | $0.00000 | $0.00281 |
Grade A, and why
drizzle 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- drizzle-orm — 86% identical, 291 lines differ
How it starts
The opening of the file, as written. The whole thing — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Drizzle ORM (this repo)
Drizzle is used in exactly one place: internal-packages/dashboard-agent-db (@internal/dashboard-agent-db), the in-dashboard agent's conversation store. Everything else in the monorepo is Prisma (@trigger.dev/database). Keep them separate.
Pinned versions: drizzle-orm ^0.45, drizzle-kit ^0.31 (dev), postgres ^3.4 (postgres.js driver). drizzle-orm and drizzle-kit are intentionally on different version lines — 0.31.x is the correct companion for 0.45.x, there is no peer dependency between them.
Critical rules
- Drizzle is only the agent's own datastore. The agent (and its task bundle) must have no access to the main Prisma database or ClickHouse. Never import the Prisma client into the agent task or into
@internal/dashboard-agent-db. Main data is reached via the API, not Drizzle. - Foreign-key-free. In cloud this DB is a separate PlanetScale database, so it can't FK into the main DB. Reference main entities (
organizationId,userId, …) by id only — never.references(). Joins happen in app code; tenant scoping is enforced in the query layer. - One dedicated Postgres schema. All tables live under
pgSchema("trigger_dashboard_agent")so they're schema-qualified and isolated from Prisma'spublicschema (this is what makes the OSS single-database fallback safe). - Pooler-safe connections. Connections go through a transaction-mode pooler (PlanetScale / PgBouncer-style), so postgres.js must run with
prepare: false— prepared statements don't survive a connection being handed to another client between checkouts. - Node16 module resolution. Relative imports need explicit
.jsextensions (import { chats } from "./schema.js"), even though the source is.ts. - Scope every user query. All queries that touch user data go through
src/queries.tsand are scoped byorganizationId/userId, so callers can't forget thewhere. Don't write ad-hoc cross-tenant queries elsewhere.
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 · 192 lines · 0 tokens per session scan A d90f2971f953
drizzle is a skill published in the GitHub repository triggerdotdev/trigger.dev (16,614 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,807 tokens. 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
sql-reporting
Conventions and review steps for writing analytics SQL against the warehouse. Use whenever the task involves querying tables, building a report, or aggregating metrics.
migrating-world-v4-to-v5
Upgrades a custom Workflow SDK World implementation from the v4 spec, or from a 5.0.0 beta, to the current v5 spec (spec version 8). Use when a package implements the World interface from @workflow/world and is moving to 5.x, or is on a 5.0.0 beta and the runtime reports This Workflow runtime supports Worlds with spec…
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.
agency-os
Notion-as-source-of-truth dispatch board for running your work like an AI agency. One Tasks database is the source of truth; tasks flow Suggestion through Discussion, To-Do, In Progress, and Done with subtasks, recurring cadences, dependencies, and template subtrees. Batch execution fans approved To-Do rows out to…