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/executing-commandsgit 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.00154 | $0.00154 |
| Opus 5 | $0.00077 | $0.00077 |
| Sonnet 5 | $0.00031 | $0.00031 |
| Haiku 4.5 | $0.00015 | $0.00015 |
Grade A, and why
executing-commands 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- executing-commands — 100% identical, 0 lines differ
What it actually says
Almost all commands in the monorepo should be executed when pnpm run ... from the root of the monorepo. For example, running tests for the @internal/run-engine internal package:
pnpm run dev --filter webapp
But often, when running tests, it's better to cd into the directory and then run tests:
cd apps/webapp
pnpm run test --run
This way you can run for a single file easily:
cd internal-packages/run-engine
pnpm run test ./src/engine/tests/ttl.test.ts --run
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 · 25 lines · 154 tokens per session scan A 3b32c58fea42
executing-commands is a cursor rule published in the GitHub repository triggerdotdev/trigger.dev (16,165 stars, last pushed 2d ago), licensed Apache-2.0. It adds 154 tokens to every session, about $0.0008 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 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.