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/arjshiv/localutils-mcp-server/typescriptgit clone --depth 1 https://github.com/arjshiv/localutils-mcp-serverWhat 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.00339 |
| Opus 5 | $0.00000 | $0.00169 |
| Sonnet 5 | $0.00000 | $0.00068 |
| Haiku 4.5 | $0.00000 | $0.00034 |
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 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 Coding Standards
File Organization
- Use named exports over default exports
- Group imports in the following order:
- Node built-in modules
- External dependencies
- Internal modules
- Separate import groups with blank lines
Type Safety
- Avoid using
anytype - Use explicit type annotations for function parameters and return types
- Prefer interfaces over type aliases for object types
- Use union types for values that can be one of several types
Naming Conventions
- Use PascalCase for class names and interfaces
- Use camelCase for variables, functions, and methods
- Use UPPER_SNAKE_CASE for constants
- Prefix interfaces with 'I' (e.g., ITimeService)
- Prefix type aliases with 'T' (e.g., TTimeFormat)
Functions
- Keep functions small and focused
- Use arrow functions for callbacks
- Implement proper error handling
- Add JSDoc comments for public functions
Error Handling
- Use custom error classes for domain-specific errors
- Always include error messages
- Implement proper error propagation
- Use try-catch blocks appropriately
Async Code
- Use async/await over raw promises
- Handle promise rejections properly
- Avoid nested promises
- Use Promise.all for parallel operations
Code Style
- Use 2 spaces for indentation
- Maximum line length: 100 characters
- Use semicolons
- Use single quotes for strings
- Add trailing commas in multiline objects/arrays
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 · 52 lines · 339 tokens per session scan A bb64a2c9ecb7
typescript is a cursor rule published in the GitHub repository arjshiv/localutils-mcp-server (2 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 339 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
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.