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 agentmods add skills/usrrname/cursorrules/typescriptnpx skills add usrrname/cursorrules --skill typescriptgit clone --depth 1 https://github.com/usrrname/cursorrulesWhat 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 | $0.00012 | $0.00462 |
| Opus 5 | $0.00006 | $0.00231 |
| Sonnet 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 yesterday.
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.
- yesterday First seen · 83 lines · 12 tokens per session scan A 6fdd61215dc2
typescript-standards is a skill published in the GitHub repository usrrname/cursorrules (10 stars, last pushed 4mo ago), licensed ISC. It adds 12 tokens to every session and 462 once invoked, about $0.0001 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.
Other skills, from other repositories
Release Notes Generation
Mandatory fast-mcp-telegram release workflow. Use when the user says release, merge and release, bump version, tag, gh release, PyPI publish, or Telegram version announcement.
feature-development
Feature development workflow for Telegram MCP projects. Use when implementing new features including research, planning, implementation, testing, and documentation.
sourcery-pr-cycle
Runs the PR creation and Sourcery AI review loop until merge-ready: open PR with gh, poll checks and comments, fix blocking issues, push, re-request review, repeat. Use when the user asks to create a PR, run the Sourcery cycle, address Sourcery review comments, or get a branch merge-ready after review.
telegram-patterns
Telegram-specific patterns and Telethon library usage.
Clean Up Docs Push
Code cleanup, docs update, and git push workflow.
Remove Old Logs
Remove log files older than 1 day from logs directory.