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 skills add usrrname/cursorrules --skill typescriptgit 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/skills/usrrname/cursorrules/typescript)<a href="https://agentmods.dev/skills/usrrname/cursorrules/typescript"><img src="https://agentmods.dev/badge/skills/usrrname/cursorrules/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/skills/usrrname/cursorrules/typescript"><img src="https://agentmods.dev/badge/skills/usrrname/cursorrules/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.00012 | $0.00462 |
| Opus 5.5 | $0.00005 | $0.00185 |
| Sonnet 5.5 | $0.00002 | $0.00092 |
| Haiku 4.5 | $0.00001 | $0.00046 |
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.
What it actually says
TypeScript Standards Skill
Guides you to write clean, type-safe TypeScript code following best practices.
When to Use
- Writing new TypeScript code
- Refactoring JavaScript to TypeScript
- Reviewing TypeScript for quality
- Setting up TypeScript projects
Critical Rules
Type Safety
- Always enable
strict: truein tsconfig.json - Avoid
any- useunknownwhen type is uncertain - Use explicit return types on public functions
- Enable
noImplicitAnyandstrictNullChecks
Naming Conventions
- PascalCase for types, interfaces, classes
- camelCase for variables, functions, methods
- UPPER_SNAKE_CASE for constants
- Use descriptive names, avoid abbreviations
Code Organization
- One class/interface per file (preferably)
- Group related types in dedicated files
- Export types explicitly
- Use barrel exports (index.ts) for clean imports
Best Practices
- Prefer
interfaceovertypefor object shapes - Use discriminated unions for complex state
- Leverage generics for reusable code
- Use
readonlyfor immutable properties - Prefer
const assertionsfor literal types
Workflow
- Setup: Ensure strict mode is enabled
- Write: Follow naming and type conventions
- Review: Check for
anyusage and implicit types - Refine: Add explicit types where inference fails
Examples
Good
interface User {
readonly id: string;
name: string;
email: string;
}
function getUserById(id: string): Promise<User | null> {
// Implementation
}
Bad
type User = any;
function getUser(id) {
return fetch(`/users/${id}`);
}
Related
/react-typescript- React-specific TypeScript patterns/vue3-typescript- Vue 3 TypeScript integration
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 · 83 lines · 12 tokens per session scan A 6fdd61215dc2
typescript-standards is a skill published in the GitHub repository usrrname/cursorrules (11 stars, last pushed 6mo ago), licensed ISC. It adds 12 tokens to every session and 462 once invoked, about $0.0000 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 skills, from other repositories
typescript-type-safety
Use when encountering TypeScript any types, type errors, or lax type checking - eliminates type holes and enforces strict type safety through proper interfaces, type guards, and module augmentation.
eslint-prettier-config
Configures ESLint and Prettier for consistent code quality with TypeScript, React, and modern best practices. Use when users request "ESLint setup", "Prettier config", "linting configuration", "code formatting", or "lint rules".
jsdoc-typescript-docs
Documents TypeScript code with JSDoc comments, generates API documentation, and creates type-safe documentation. Use when users request "JSDoc", "code documentation", "API docs", "TypeDoc", or "inline documentation".
typescript-strict-migrator
Migrates TypeScript projects to strict mode incrementally with type guards, utility types, and best practices. Use when users request "TypeScript strict", "strict mode migration", "type safety", "strict TypeScript", or "ts-strict".
hono
Use when building Hono web applications or when the user asks about Hono APIs, routing, middleware, JSX, validation, testing, or streaming. TRIGGER when code imports from 'hono' or 'hono/', or user mentions Hono. Use npx hono request to test endpoints.
tanstack-config
Opinionated toolkit for building, versioning, and publishing high-quality JavaScript/TypeScript packages.