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/logosdx/monorepo/typescript-patternsgit clone --depth 1 https://github.com/logosdx/monorepoWhat 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.01695 |
| Opus 5 | $0.00000 | $0.00847 |
| Sonnet 5 | $0.00000 | $0.00339 |
| Haiku 4.5 | $0.00000 | $0.00169 |
Grade A, and why
typescript-patterns 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.
How it starts
The opening of the file, as written. The whole thing — 322 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TypeScript Patterns
Comprehensive patterns for TypeScript code organization, classes, types, and symbols.
Code Style Conventions
Syntax & Formatting
- Newline after function declaration and opening blocks
- Prefer vertical space over horizontal when functions are long
- Group functions: Declaration → Validation → Business Logic → Commit
Naming Philosophy
- Use meaningful names that explain what the thing is
- ✅
userExists,fetchInvoiceTotal - ❌
x,data,handleIt
- ✅
- Functions should read like English
Comments & JSDoc
- JSDoc all functions and classes
- Explain WHY something exists — not how or what
- Always provide usage examples
Function Structure
Use our 4-block structure for complex functions:
/**
* Updates the email address for a given user.
*
* @example
* const user = await updateUserEmail(userID, newEmail);
*/
async function updateUserEmail(userID: UUID, newEmail: EmailAddress): Promise<User> {
let retryCount = 0;
if (!isValidEmail(newEmail)) {
throw new InvalidEmailError();
}
const [user, err] = await attempt(() => fetchUser(userID));
if (err || !user) {
throw new UserNotFoundError();
}
else if (user.email === newEmail) { // notice that else is not on the same line as the closing if
return user;
}
const modifiedUser = modifyUserEmail(user, newEmail);
const [ok, saveErr] = await attempt(() => saveUser(modifiedUser));
if (saveErr) {
throw saveErr;
}
return modifiedUser;
}
Where the "declaration" block is:
Declare places in a single, predictable place.
function updateUserEmail(userID: UUID, newEmail: EmailAddress): Promise<User> {
let retryCount = 0; // <-- declare vars first
// ...
}
"Validation" block is:
We validate inputs whenever appropriate to have as much predictability as possible
if (!isValidEmail(newEmail)) {
throw new InvalidEmailError();
}
const [user, err] = await attempt(() => fetchUser(userID));
if (err || !user) {
throw new UserNotFoundError();
}
else if (user.email === newEmail) { // notice that else is not on the same line as the closing if
return user;
}
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 · 322 lines · 1,695 tokens per session scan A d7edc530ebd9
typescript-patterns is a cursor rule published in the GitHub repository logosdx/monorepo (7 stars, last pushed 16d ago), licensed BSD-3-Clause. It costs nothing until one of its globs matches a file; then it loads 1,695 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.