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 skills/triggerdotdev/trigger.dev/trigger-realtime-and-frontendnpx skills add triggerdotdev/trigger.dev --skill trigger-realtime-and-frontendgit 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.00148 | $0.00912 |
| Opus 5 | $0.00074 | $0.00456 |
| Sonnet 5 | $0.00030 | $0.00182 |
| Haiku 4.5 | $0.00015 | $0.00091 |
Grade A, and why
trigger-realtime-and-frontend 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.
How it starts
The opening of the file, as written. The whole thing — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Realtime and Frontend
The full, version-pinned reference 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-realtime-and-frontend/SKILL.md— run subscriptions,@trigger.dev/react-hooks, streams, frontend triggering, and scoped tokens. - Docs: the full, version-pinned docs ship bundled at
node_modules/@trigger.dev/sdk/docs/realtime/; the skill above lists the exact pages it draws from in itssources:frontmatter. Grep for a hook, e.g.grep -rl "useRealtimeRun" 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.
Common mistakes
-
CRITICAL: Triggering from the browser with a Public Access Token. The read token from
createPublicTokencannot trigger tasks.- Wrong:
useTaskTrigger("my-task", { accessToken: publicAccessTokenFromCreatePublicToken }) - Correct: mint a single-use Trigger Token with
auth.createTriggerPublicToken("my-task")and pass that.
- Wrong:
-
Token with no scopes. A scopeless token authorizes nothing, so every subscribe 403s.
- Wrong:
await auth.createPublicToken() - Correct:
await auth.createPublicToken({ scopes: { read: { runs: ["run_1234"] } } })
- Wrong:
-
Polling with
useRun/SWR for live updates.useRunis the SWR-based management-API hook (not recommended for live state); setrefreshInterval: 0to stop polling if you do use it.- Wrong:
useRun(runId, { refreshInterval: 1000 })to track progress - Correct:
useRealtimeRun(runId, { accessToken })(no polling, no WebSocket setup)
- Wrong:
-
Forgetting
"use client". Realtime/trigger hooks cannot run in a server component.- Wrong: a Next.js App Router server component using
useRealtimeRun - Correct: put
"use client";at the top of any component using these hooks.
- Wrong: a Next.js App Router server component using
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 · 59 lines · 148 tokens per session scan A 86ff10408cbc
trigger-realtime-and-frontend is a skill published in the GitHub repository triggerdotdev/trigger.dev (16,165 stars, last pushed 2d ago), licensed Apache-2.0. It adds 148 tokens to every session and 912 once invoked, about $0.0007 per session on Opus 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
clone-website
Reverse-engineer and clone a website in one shot — extracts assets, CSS, and content section-by-section and proactively dispatches parallel builder agents in worktrees as it goes. Use this whenever the user wants to clone, replicate, rebuild, reverse-engineer, or copy any website. Also triggers on phrases like "make a…
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-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-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.