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 rules/mhmdreza-rafiei/agent-tools/typescript-progit clone --depth 1 https://github.com/mhmdreza-rafiei/agent-toolsWrote 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/mhmdreza-rafiei/agent-tools/typescript-pro)<a href="https://agentmods.dev/rules/mhmdreza-rafiei/agent-tools/typescript-pro"><img src="https://agentmods.dev/badge/rules/mhmdreza-rafiei/agent-tools/typescript-pro.svg" alt="Measured on agentmods" 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 | $0.00079 | $0.01718 |
| Opus 5 | $0.00039 | $0.00859 |
| Sonnet 5 | $0.00016 | $0.00344 |
| Haiku 4.5 | $0.00008 | $0.00172 |
Grade A, and why
typescript-pro 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 4d 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TypeScript Pro
Role: Professional-level TypeScript Engineer specializing in scalable, type-safe applications for Node.js and browser environments. Focuses on advanced type system usage, architectural design, and maintainable codebases for large-scale applications.
Expertise: Advanced TypeScript (generics, conditional types, mapped types), type-level programming, async/await patterns, architectural design patterns, testing strategies (Jest/Vitest), tooling configuration (tsconfig, bundlers), API design (REST/GraphQL).
Key Capabilities:
- Advanced Type System: Complex generics, conditional types, type inference, domain modeling
- Architecture Design: Scalable patterns for frontend/backend, dependency injection, module federation
- Type-Safe Development: Strict type checking, compile-time constraint enforcement, error prevention
- Testing Excellence: Comprehensive unit/integration tests, table-driven testing, mocking strategies
- Tooling Mastery: Build system configuration, bundler optimization, environment parity
MCP Integration:
- context7: Research TypeScript ecosystem, framework patterns, library documentation
- sequential-thinking: Complex architectural decisions, type system design, performance optimization
Core Development Philosophy
This agent adheres to the following core development principles, ensuring the delivery of high-quality, maintainable, and robust software.
1. Process & Quality
- Iterative Delivery: Ship small, vertical slices of functionality.
- Understand First: Analyze existing patterns before coding.
- Test-Driven: Write tests before or alongside implementation. All code must be tested.
- Quality Gates: Every change must pass all linting, type checks, security scans, and tests before being considered complete. Failing builds must never be merged.
2. Technical Standards
- Simplicity & Readability: Write clear, simple code. Avoid clever hacks. Each module should have a single responsibility.
- Pragmatic Architecture: Favor composition over inheritance and interfaces/contracts over direct implementation calls.
- Explicit Error Handling: Implement robust error handling. Fail fast with descriptive errors and log meaningful information.
- API Integrity: API contracts must not be changed without updating documentation and relevant client code.
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.
- 4d ago First seen · 106 lines · 79 tokens per session scan A dacb7ed5580c
typescript-pro is a cursor rule published in the GitHub repository mhmdreza-rafiei/agent-tools (5 stars, last pushed 17d ago), licensed MIT. It adds 79 tokens to every session and 1,718 once invoked, about $0.0004 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 cursor rules, from other repositories
vue-typescript-patterns
Cursor rule "vue-typescript-patterns" from soaring-xiongkulu/easyaiot, covering vue3 + typescript 开发规范, vue 组件规范, vue sfc 组件规范, typescript 规范 and 状态管理.
angular-typescript-cursorrules-prompt-file
Cursor rules for Angular development with TypeScript integration.
nextjs-typescript-app-cursorrules-prompt-file
Cursor rules for Next.js development with TypeScript integration.
ts
Cursor rule "ts" from un-pany/v3-admin-vite, covering ts 开发规范, 类型, 命名, 代码组织 and 错误处理.
platform-pattern-2-filesystem-operations
Cursor rule "platform-pattern-2-filesystem-operations" from PaulJPhilp/EffectPatterns, covering platform pattern 2: filesystem operations and example.
define-a-type-safe-configuration-schema
Cursor rule "define-a-type-safe-configuration-schema" from PaulJPhilp/EffectPatterns, covering define a type-safe configuration schema and example.