standard-typescript-good-practices

A short set of general rules for writing TypeScript code in an application. TypeScript is JavaScript with syntax for describing and checking data types before code runs.

In plain words
What is it for?
Use it when defining errors or presentation data objects, especially when adding fields to existing domain types.
Why use it?
It prevents a few recurring code-quality problems, such as unsafe error definitions and manually duplicated data shapes that can drift apart.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/packmindhub/packmind/standard-typescript-good-practices
Clone the repo
git clone --depth 1 https://github.com/PackmindHub/packmind

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 131 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00131
Opus 5 $0.00000 $0.00066
Sonnet 5 $0.00000 $0.00026
Haiku 4.5 $0.00000 $0.00013

Measured 2d ago against content hash f246e8821d35, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

standard-typescript-good-practices 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 2d 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.

.cursor/rules/packmind/standard-typescript-good-practices.mdc · 11 lines

What it actually says

Standard: Typescript good practices

Generic practices that can be applied for all TS code in our app :

  • Do not use Object.setPrototypeOf when defining errors.
  • When defining a presentation DTO that enriches a domain type, use an intersection type (DomainType & { extraField: T }) instead of manually re-declaring the domain type's fields, so that structural drift is caught at compile time.

Full standard is available here for further request: Typescript good practices

Changes

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.

  1. 2d ago First seen · 11 lines · 131 tokens per session scan A f246e8821d35

Subscribe to this mod's changes

standard-typescript-good-practices is a cursor rule published in the GitHub repository PackmindHub/packmind (306 stars, last pushed 5d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 131 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-30.