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 agentmods add rules/triggerdotdev/trigger.dev/webappgit clone --depth 1 https://github.com/triggerdotdev/trigger.devWhat 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 | $0.00000 | $0.01176 |
| Opus 5 | $0.00000 | $0.00588 |
| Sonnet 5 | $0.00000 | $0.00235 |
| Haiku 4.5 | $0.00000 | $0.00118 |
Grade A, and why
webapp 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 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.
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:
- webapp — 98% identical, 2 lines differ
How it starts
The opening of the file, as written. The whole thing — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The main trigger.dev webapp, which powers it's API and dashboard and makes up the docker image that is produced as an OSS image, is a Remix 2.17.4 app that uses an express server, written in TypeScript. The following subsystems are either included in the webapp or are used by the webapp in another part of the monorepo:
@trigger.dev/databaseexports a Prisma 6.14.0 client that is used extensively in the webapp to access a PostgreSQL instance. The schema file is schema.prisma@trigger.dev/coreis a published package and is used to share code between the@trigger.dev/sdkand the webapp. It includes functionality but also a load of Zod schemas for data validation. When importing from@trigger.dev/corein the webapp, we never import the root@trigger.dev/corepath, instead we favor one of the subpath exports that you can find in package.json@internal/run-enginehas all the code needed to trigger a run and take it through it's lifecycle to completion.@trigger.dev/redis-workeris a custom redis based background job/worker system that's used in the webapp and also used inside the run engine.
Environment variables and testing
In the webapp, all environment variables are accessed through the env export of env.server.ts, instead of directly accessing process.env.
Ideally, the env.server.ts file would never be imported into a test file, either directly or indirectly. Tests should only imported classes and functions from a file matching app/**/*.ts of the webapp, and that file should not use environment variables, everything should be passed through as options instead. This "service/configuration" separation is important, and can be seen in a few places in the code for examples:
- realtimeClient.server.ts is the testable service, and realtimeClientGlobal.server.ts is the configuration
Also for writing tests in the webapp, checkout our tests.md guide
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.
- 2d ago First seen · 41 lines · 0 tokens per session scan A ab6151bea4e9
webapp is a cursor rule published in the GitHub repository triggerdotdev/trigger.dev (16,165 stars, last pushed 2d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,176 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 cursor rules, from other repositories
workflow-deployment
Workflow testing and deployment process guide.
swc-plugin
The specification for how to plugin is meant to work can be found in spec.md.
test-running
When running tests, use the --watch false flag to avoid watch mode.
docs
This file provides guidelines for working with the documentation in the /docs directory.
codex-premium-website-skills
Apply Codex Skills standards to frontend, website, motion, accessibility, QA, agent reasoning, and handoff work.
middleware-auth
Next.js middleware auth — prevents auth logic being placed in middleware instead of route handlers.