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/usrrname/cursorrulesWrote 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/usrrname/cursorrules/typescript-standards-auto)<a href="https://agentmods.dev/rules/usrrname/cursorrules/typescript-standards-auto"><img src="https://agentmods.dev/badge/rules/usrrname/cursorrules/typescript-standards-auto/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/usrrname/cursorrules/typescript-standards-auto"><img src="https://agentmods.dev/badge/rules/usrrname/cursorrules/typescript-standards-auto.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.00984 |
| Opus 5.5 | $0.00000 | $0.00394 |
| Sonnet 5.5 | $0.00000 | $0.00197 |
| Haiku 4.5 | $0.00000 | $0.00098 |
Grade A, and why
typescript-standards 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TypeScript Standards
Critical Rules
- Refer to https://www.typescriptlang.org/tsconfig when tsconfig.json values are changed.
- Use strict mode with
"strict": truein tsconfig.json - Remind user the limitations of using esModuleInterop and allowSyntheticDefaultImports in tsconfig.json https://www.typescriptlang.org/tsconfig/#Interop_Constraints_6252
- Explicitly declare types for function parameters and return values
- Avoid using
anytype unless absolutely necessary. Useunknowninstead. - Use interfaces for object type definitions
- Use enums for fixed sets of values
- Use type aliases to simplify complex types
- Document APIs with JSDoc comments
- Maintain proper error handling with typed errors
- Use type guards and type narrowing to improve type safety
- Use type literals and unions to define the exact allowed values.
- Use type assertions and annotations when necessary. They are unnecessary if type inference is possible.
- Use type unions and intersections to combine types.
- Export types from modules using the
export typesyntax - If using an existing library with types, import the types using the
import typesyntax - Declare types for file extensions that aren't supported by the compiler using the
declare modulesyntax - If using node 23+, use
node --experimental-strip-typesin package.json scripts to strip types when running the code locally - Use utility types as much as possible to avoid type duplication.
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 · 119 lines · 984 tokens per session scan A a3ca8a2c600c
typescript-standards is a cursor rule published in the GitHub repository usrrname/cursorrules (11 stars, last pushed 6mo ago), licensed ISC. It costs nothing until one of its globs matches a file; then it loads 984 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
angular
Angular: signals, standalone components, RxJS patterns.
typescript
Strict TypeScript: generics, discriminated unions, no any.
bun
Bun runtime: Bun.serve, Bun.file, bundler, test runner.
deno
Deno: permissions, deno.json, std library, Deploy.
typescript
TypeScript best practices.
nextjs-tanstack-query-cursorrules-prompt-file
Cursor rules for Next.js App Router with TanStack Query v5, covering the HydrationBoundary pattern, Server Actions as mutations, and optimistic updates.