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/inboxpraveen/minimize-cursor-cost/typescriptgit clone --depth 1 https://github.com/inboxpraveen/Minimize-Cursor-CostWrote 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/inboxpraveen/minimize-cursor-cost/typescript)<a href="https://agentmods.dev/rules/inboxpraveen/minimize-cursor-cost/typescript"><img src="https://agentmods.dev/badge/rules/inboxpraveen/minimize-cursor-cost/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.00000 | $0.00349 |
| Opus 5 | $0.00000 | $0.00175 |
| Sonnet 5 | $0.00000 | $0.00070 |
| Haiku 4.5 | $0.00000 | $0.00035 |
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 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.
What it actually says
TypeScript/JavaScript Rules
Style Matching
- Match existing: semicolons or not, single vs double quotes, trailing commas
- Match existing:
functiondeclarations vs arrow functions - Match existing:
interfacevstypealias preference - Do not add
as constor other TS niceties if the file doesn't already use them
Output Format
- Single function change → show only that function
- React component change → show only the changed JSX section + affected hooks
- Use
// ... rest of componentto skip unchanged JSX
Types
- Reuse existing project types — check for them before creating new ones
- Inline types for one-use cases:
(items: string[]) =>not a new interface - Don't add
unknownor overly defensive types unless the existing code does
Imports
- Show only new/changed import lines
- Group: external libs → internal modules → types (match existing grouping)
React Specifics
- Don't rename props or state variables
- Don't extract new components unless asked
- Don't add
useMemo/useCallbackoptimizations unless the task is performance - Don't switch between controlled/uncontrolled input patterns
Never
- Don't convert
.jsto.tsunless asked - Don't add JSDoc to functions that don't have it
- Don't wrap with try/catch unless existing similar functions have it
- Don't add default exports if the file uses named exports
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 · 40 lines · 0 tokens per session scan A 7f883c7f23b1
typescript is a cursor rule published in the GitHub repository inboxpraveen/Minimize-Cursor-Cost (7 stars, last pushed 19d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 349 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
vibe
TS/JS roof. Detect Next vs Vite vs Astro before APIs. Index only.
sample_cursor_rule
React component best practices.
typescript
TypeScript 编码规则和最佳实践.
typescript
TypeScript Development Standards.
typescript
TypeScript best practices.
app_feature_first_architecture
Feature-first architecture is a design pattern that organizes code by business features rather than technical layers. This approach promotes better maintainability, scalability, and team collaboration by keeping related functionality together and reducing coupling between different parts of the application.