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.
git clone --depth 1 https://github.com/maccman/agent-playgroundWrote 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/rules/maccman/agent-playground/es-module-compatibility)<a href="https://agentmods.dev/rules/maccman/agent-playground/es-module-compatibility"><img src="https://agentmods.dev/badge/rules/maccman/agent-playground/es-module-compatibility/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/rules/maccman/agent-playground/es-module-compatibility"><img src="https://agentmods.dev/badge/rules/maccman/agent-playground/es-module-compatibility.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00498 | $0.00498 |
| Opus 5.5 | $0.00199 | $0.00199 |
| Sonnet 5.5 | $0.00100 | $0.00100 |
| Haiku 4.5 | $0.00050 | $0.00050 |
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 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.
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.urlfor entry point detection instead ofrequire.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
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 · 101 lines · 498 tokens per session scan A 7a60ddb79c92
es-module-compatibility is a cursor rule published in the GitHub repository maccman/agent-playground (2 stars, last pushed 7mo ago), licensed MIT. It adds 498 tokens to every session, about $0.0020 per session on Opus 5.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.
Other cursor rules, from other repositories
vue-typescript-patterns
A set of coding rules for Vue 3 projects using TypeScript, a language that adds type checking to JavaScript. It covers component structure, file locations, TypeScript usage, and Pinia, a library for shared application state.
typescript-security
// NEVER: Hardcoded secrets const apiKey = "sk-proj-xxxxx".
nextjs-typescript-app-cursorrules-prompt-file
Cursor rules for Next.js development with TypeScript integration.
ts
A set of TypeScript coding rules covering types, naming, file organization, error handling, and strict type checking. TypeScript is JavaScript with checks that help catch many mistakes before the program runs.
general-rule
Cursor rule "general-rule" from vinhnx/vtchat, covering development guidelines, tech stack & project overview, package management, code style and ui/ux design principles.
platform-pattern-2-filesystem-operations
Cursor rule "platform-pattern-2-filesystem-operations" from PaulJPhilp/EffectPatterns, covering platform pattern 2: filesystem operations and example.