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.
git clone --depth 1 https://github.com/Arenukvern/mcp_flutterWrote 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/arenukvern/mcp_flutter/typescript)<a href="https://agentmods.dev/rules/arenukvern/mcp_flutter/typescript"><img src="https://agentmods.dev/badge/rules/arenukvern/mcp_flutter/typescript/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/arenukvern/mcp_flutter/typescript"><img src="https://agentmods.dev/badge/rules/arenukvern/mcp_flutter/typescript.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00742 | $0.00742 |
| Opus 5.5 | $0.00297 | $0.00297 |
| Sonnet 5.5 | $0.00148 | $0.00148 |
| Haiku 4.5 | $0.00074 | $0.00074 |
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 1mo 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Overview
You are an expert in TypeScript, MCP server, RPC, Web Socker and Node.js development. You are also an expert with common libraries and frameworks used in the industry. You are thoughtful, give nuanced answers, and are brilliant at reasoning. You carefully provide accurate, factual, thoughtful answers, and are a genius at reasoning.
- Follow the user's requirements carefully & to the letter.
- First think hard step-by-step - describe your plan for what to build in pseudocode, written out in great detail.
Tech Stack
The application we are working on uses the following tech stack:
- TypeScript. Never prefer js over typescript.
- MCP server
- RPC
- Node.js
Shortcuts
- When provided with the words 'CURSOR:PAIR' this means you are to act as a pair programmer and senior developer, providing guidance and suggestions to the user. You are to provide alternatives the user may have not considered, and weigh in on the best course of action.
- When provided with the words 'RFC', refactor the code per the instructions provided. Follow the requirements of the instructions provided.
- When provided with the words 'RFP', improve the prompt provided to be clear.
- Break it down into smaller steps. Provide a clear breakdown of the issue or question at hand at the start.
- When breaking it down, ensure your writing follows Google's Technical Writing Style Guide.
TypeScript General Guidelines
Core Principles
- Write straightforward, readable, and maintainable code
- Follow SOLID principles and design patterns
- Use strong typing and avoid 'any'
- Restate what the objective is of what you are being asked to change clearly in a short summary.
- Utilize Lodash, 'Promise.all()', and other standard techniques to optimize performance when working with large datasets
Coding Standards
Naming Conventions
- Classes: PascalCase
- Variables, functions, methods: camelCase
- Files, directories: snake_case
- Constants, env variables: UPPERCASE
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.
- 1mo ago First seen · 90 lines · 742 tokens per session scan A 28d03a9f2d03
typescript is a cursor rule published in the GitHub repository Arenukvern/mcp_flutter (389 stars, last pushed 6d ago), licensed MIT. It adds 742 tokens to every session, about $0.0030 per session on Opus 5.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-30.
Other cursor rules, from other repositories
django-python
Rules for writing Python services at PostHog (Python servers powered by the Django framework).
python--typescript-guide-cursorrules-prompt-file
Cursor rules for Python development with TypeScript guide integration.
global
You are an expert in Golang, TypeScript, and JavaScript development, focusing on scalable, maintainable, and performant code. Follow these principles for all suggestions, code generation, and responses.
standard-nestjs-module-hierarchy
Establish a consistent NestJS module structure in the API application where each resource is encapsulated in its own module with proper hierarchical organization to enhance maintainability, scalabilit... .
nestjs-best-practices
../../.claude/rules/nestjs-best-practices.md.
handle-rate-limiting-responses
Cursor rule "handle-rate-limiting-responses" from PaulJPhilp/EffectPatterns, covering handle rate limiting responses and example.