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/PackmindHub/packmindWrote 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/packmindhub/packmind/standard-typescript-good-practices)<a href="https://agentmods.dev/rules/packmindhub/packmind/standard-typescript-good-practices"><img src="https://agentmods.dev/badge/rules/packmindhub/packmind/standard-typescript-good-practices/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/packmindhub/packmind/standard-typescript-good-practices"><img src="https://agentmods.dev/badge/rules/packmindhub/packmind/standard-typescript-good-practices.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.00131 | $0.00131 |
| Opus 5.5 | $0.00052 | $0.00052 |
| Sonnet 5.5 | $0.00026 | $0.00026 |
| Haiku 4.5 | $0.00013 | $0.00013 |
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 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.
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.setPrototypeOfwhen 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
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 · 11 lines · 131 tokens per session scan A f246e8821d35
standard-typescript-good-practices is a cursor rule published in the GitHub repository PackmindHub/packmind (319 stars, last pushed 2d ago), licensed Apache-2.0. It adds 131 tokens to every session, about $0.0005 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
cursorrules
Cursor rule "cursorrules" from googlarz/agents-sync, covering .cursorrules — managed by agents-sync v1.0.0, language: typescript / next.js 14 and run tests: npm test.
component-development
Modern React + TypeScript component patterns — hooks, typed props, performance optimization, forms, and testing.
typescript
TypeScript type definitions and utility patterns for the application.
typescript
TypeScript conventions.
ecoconception-javascript
Règles d'écoconception pour le code JavaScript et TypeScript, navigateur comme Node.js.
ts
A set of TypeScript coding rules covering types, naming, file organization, error handling, and strict type checking. TypeScript is JavaScript with checks that help catch many mistakes before the program runs.