es-module-compatibility

A coding rule for TypeScript scripts that must work both when imported and when run directly as ES modules. ES modules are JavaScript's standard import-and-export format.

In plain words
What is it for?
Use it when creating runnable TypeScript files, especially scripts in a scripts/ folder. It guides direct-execution detection, file-path handling, imports, environment-variable loading, and script structure.
Why use it?
It prevents scripts from failing because they use CommonJS-only checks or file-path variables that are unavailable in ES modules.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/maccman/agent-playground/es-module-compatibility
Clone the repo
git clone --depth 1 https://github.com/maccman/agent-playground

Made for: Cursor.

Per session 498 This file is loaded in full into every session.
When invoked 498 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00498 $0.00498
Opus 5 $0.00249 $0.00249
Sonnet 5 $0.00100 $0.00100
Haiku 4.5 $0.00050 $0.00050

Measured 2d ago against content hash 7a60ddb79c92, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

es-module-compatibility 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.

.cursor/rules/es-module-compatibility.mdc · 101 lines

How it starts

The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.

ES Module Compatibility Guide

Script Entry Point Detection

When creating TypeScript scripts that can be both imported and executed directly, use ES module-compatible patterns:

// ❌ CommonJS pattern (doesn't work with tsx/ES modules)
if (require.main === module) {
  main().catch(console.error)
}

// ✅ ES module pattern
if (import.meta.url === `file://${process.argv[1]}`) {
  main().catch(console.error)
}

File Path Utilities for ES Modules

When you need __filename and __dirname equivalents in ES modules:

import { fileURLToPath } from 'url'
import path from 'path'

// Get current file path for ES modules
const __filename = fileURLToPath(import.meta.url)
const __dirname = path.dirname(__filename)

Import Patterns

Use consistent ES module import syntax:

// ✅ Preferred imports
import { config } from 'dotenv'
import fs from 'fs'
import path from 'path'

// Load environment variables early
config()

TypeScript Script Structure

For runnable TypeScript scripts in the scripts/ directory:

import { config } from 'dotenv'
import { fileURLToPath } from 'url'
import path from 'path'

// Load environment variables
config()

// ES module file path utilities
const __filename = fileURLToPath(import.meta.url)
const __dirname = path.dirname(__filename)

// Main implementation
class MyScript {
  // Implementation here
}

async function main() {
  // Script logic here
}

// Run script if executed directly
if (import.meta.url === `file://${process.argv[1]}`) {
  main().catch(console.error)
}

// Export for potential imports
export { MyScript }

Running Scripts

Use pnpm start or tsx to run TypeScript scripts:

pnpm start scripts/my-script.ts
# or
tsx scripts/my-script.ts

Key Points

  • Always use ES module syntax (import/export) in TypeScript files
  • Use import.meta.url for entry point detection instead of require.main
  • Include proper error handling with .catch(console.error)
  • Load environment variables with config() at the top of scripts
  • Export classes/functions for potential reuse while allowing direct execution

Read the full file on GitHub · 101 lines

Changes

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.

  1. 2d ago First seen · 101 lines · 498 tokens per session scan A 7a60ddb79c92

Subscribe to this mod's changes

es-module-compatibility is a cursor rule published in the GitHub repository maccman/agent-playground (2 stars, last pushed 6mo ago), licensed MIT. It adds 498 tokens to every session, about $0.0025 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-31.