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/packmindhub/packmind/standard-typescript-good-practicesgit clone --depth 1 https://github.com/PackmindHub/packmindWhat 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.00131 |
| Opus 5 | $0.00000 | $0.00066 |
| Sonnet 5 | $0.00000 | $0.00026 |
| Haiku 4.5 | $0.00000 | $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 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.
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.
- 2d 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 (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.
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.
valid
TypeScript coding standards for the project.
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.
cursorrules
Cursor rule "cursorrules" from Wolfe-Jam/faf-cli, covering faf:start, .cursorrules, authored from project.faf — faf-cli v6, stack and faf:end.
typescript
Here's how frontend code is organized in web/app/.