Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/jeffgreendesign/textrawlnpx agentmods add rules/jeffgreendesign/textrawl/typescriptWrote 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/jeffgreendesign/textrawl/typescript)<a href="https://agentmods.dev/rules/jeffgreendesign/textrawl/typescript"><img src="https://agentmods.dev/badge/rules/jeffgreendesign/textrawl/typescript/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/jeffgreendesign/textrawl/typescript"><img src="https://agentmods.dev/badge/rules/jeffgreendesign/textrawl/typescript.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.00000 | $0.00279 |
| Opus 5.5 | $0.00000 | $0.00112 |
| Sonnet 5.5 | $0.00000 | $0.00056 |
| Haiku 4.5 | $0.00000 | $0.00028 |
Grade A, and why
typescript 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.
What it actually says
TypeScript Conventions
ESM Imports
This is an ES module project. All imports MUST use .js extensions:
// Correct
import { logger } from '../utils/logger.js';
import { hybridSearch } from '../db/search.js';
// Wrong - will fail at runtime
import { logger } from '../utils/logger';
Node.js Version
Requires Node.js >= 22.0.0. Use modern APIs:
fetch(native, no node-fetch)- Top-level await in modules
- ES2023+ features
Type Definitions
- Define types in
src/types/directory - Export types from module index files
- Use Zod for runtime validation, infer types with
z.infer<>
Async/Await
Always use async/await over raw promises:
// Correct
const result = await someAsyncOperation();
// Avoid
someAsyncOperation().then(result => { ... });
Error Handling
Use custom error hierarchy from src/utils/errors.ts:
import { NotFoundError, ValidationError } from '../utils/errors.js';
if (!document) {
throw new NotFoundError('Document not found');
}
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 · 58 lines · 0 tokens per session scan A ee8e5e3c026d
typescript is a cursor rule published in the GitHub repository jeffgreendesign/textrawl (5 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 279 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-31.
Other cursor rules, from other repositories
svelte
You are an expert in Svelte 5, SvelteKit, TypeScript, and modern web development.
npm-cli-packaging-agent
Apply when preparing a TypeScript CLI tool for distribution via npm, specifically when configuring package.json, handling executables, and considering cross-platform compatibility. Covers the bin field, shebang line (#!/usr/bin/env node), pre-publish checks, installation instructions, and Node engine compatibility.
ts-dependency-management-agent
Apply when adding, removing, or managing dependencies, or when structuring code modules in a TypeScript project, especially for CLIs. Promotes minimizing external dependencies, using lockfiles (package-lock.json), vetting dependencies, following SOLID principles for modular code, and using dependency injection for…
ts-cli-argument-handling-agent
Apply when implementing command-line argument validation or interactive user prompts in a TypeScript CLI. Guides towards rigorous validation, clear error messages, user-friendly interactive fallbacks (e.g., using Inquirer.js) for missing inputs, sensible defaults, and support for non-interactive execution modes (e.g.…
ts-cli-command-definition-agent
Apply when defining or modifying CLI commands, subcommands, and options in a TypeScript project, particularly when using libraries like Commander.js or Yargs. Ensures use of robust parsing, POSIX-style flags, descriptive names, clear argument notation, and separation of parsing from implementation logic.
ts-cli-project-structure-agent
Apply when discussing or modifying the project structure of a TypeScript CLI tool. Ensures adherence to conventional layouts (bin/, src/commands/, src/utils/, src/lib/) for better navigation, scalability, and testability, especially when organizing source code, build outputs, and configuration.