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/girijashankarj/cursor-handbook/typescriptgit clone --depth 1 https://github.com/girijashankarj/cursor-handbookWrote 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/girijashankarj/cursor-handbook/typescript)<a href="https://agentmods.dev/rules/girijashankarj/cursor-handbook/typescript"><img src="https://agentmods.dev/badge/rules/girijashankarj/cursor-handbook/typescript.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.00140 | $0.00140 |
| Opus 5 | $0.00070 | $0.00070 |
| Sonnet 5 | $0.00028 | $0.00028 |
| Haiku 4.5 | $0.00014 | $0.00014 |
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 today.
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
Backend: TypeScript
Strictness
- Prefer strict mode (strictNullChecks, strict); avoid
any; useunknownfor unvalidated input. - Define interfaces for request/response and domain types; keep them in common or types directories.
Types
- Export types from a single place per domain (e.g. order.types.ts); avoid duplicating type definitions.
- Use branded types or Zod/inferred types for validated payloads at the API boundary.
Conventions
- Run type-check as the default validation step; do not run full test suite without confirmation.
- Follow backend handler-patterns and code-organization; use explicit return types for public functions.
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.
- today First seen · 14 lines · 140 tokens per session scan A b2e9135f9f09
typescript is a cursor rule published in the GitHub repository girijashankarj/cursor-handbook (30 stars, last pushed 4d ago), licensed MIT. It adds 140 tokens to every session, about $0.0007 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-09-03.
Other cursor rules, from other repositories
graphstack
GraphStack v4.7.1 — Orchestrated, graph-first, GNAP-tracked AI development (cross-platform).
code-optimization
Guidelines for optimizing duplicate and poorly structured code.
mcp
Guidelines for implementing and interacting with the Task Master MCP Server.
new_features
Guidelines for integrating new features into the Task Master CLI.
commands
Guidelines for implementing CLI commands using Commander.js.
git_workflow
Git workflow integrated with Task Master for feature development and collaboration.