standard-back-end-repositories-sql-queries-using-typeorm

standard-back-end-repositories-sql-queries-using-typeorm is a cursor rule for Cursor from PackmindHub/packmind. It costs 216 tokens per session, scanned A, original, Apache-2.0.

A coding standard for writing database queries with TypeORM in backend repository files. TypeORM is a library that lets TypeScript or JavaScript applications work with databases.

In plain words
What is it for?
Guiding repository code that reads database records, including queries involving soft-deleted data, multiple-value filters, and query options.
Why use it?
It reduces unsafe or inconsistent queries by requiring parameterized conditions, correct handling of deleted records, and proper filtering for lists of values.

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-back-end-repositories-sql-queries-using-typeorm
Clone the repo
git clone --depth 1 https://github.com/PackmindHub/packmind

Made for: Cursor.

Wrote 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.

agentmods badge for standard-back-end-repositories-sql-queries-using-typeorm

README.md
[![agentmods](https://agentmods.dev/badge/rules/packmindhub/packmind/standard-back-end-repositories-sql-queries-using-typeorm.svg)](https://agentmods.dev/rules/packmindhub/packmind/standard-back-end-repositories-sql-queries-using-typeorm)
Your own site
<a href="https://agentmods.dev/rules/packmindhub/packmind/standard-back-end-repositories-sql-queries-using-typeorm"><img src="https://agentmods.dev/badge/rules/packmindhub/packmind/standard-back-end-repositories-sql-queries-using-typeorm.svg" alt="Measured on agentmods" height="20"></a>
Per session 216 This file is loaded in full into every session.
When invoked 216 The same file — it is already loaded in full.
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.00216 $0.00216
Opus 5 $0.00108 $0.00108
Sonnet 5 $0.00043 $0.00043
Haiku 4.5 $0.00022 $0.00022

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

Security

Grade A, and why

standard-back-end-repositories-sql-queries-using-typeorm 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 5d 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.

packages/.cursor/rules/packmind/standard-back-end-repositories-sql-queries-using-typeorm.mdc · 12 lines

What it actually says

Standard: Back-end repositories SQL queries using TypeORM

This standard provides guidelines for writing SQL queries using TypeORM in back-end repositories located in /infra/repositories/*Repository.ts. TypeORM offers multiple approaches to query data, but f... :

  • Handle soft-deleted entities properly using withDeleted() or includeDeleted options. Always respect the QueryOption parameter when provided, and only include deleted entities when explicitly requested.
  • Use IN clause with array parameterization for filtering by multiple values. Always pass arrays as spread parameters using :...paramName syntax to ensure proper parameterization.
  • Use TypeORM's QueryBuilder with parameterized queries instead of raw SQL strings. Always pass parameters as objects to where(), andWhere(), and other query methods to prevent SQL injection and ensure type safety.

Full standard is available here for further request: Back-end repositories SQL queries using TypeORM

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. 5d ago First seen · 12 lines · 216 tokens per session scan A 47c6d161d144

Subscribe to this mod's changes

standard-back-end-repositories-sql-queries-using-typeorm is a cursor rule published in the GitHub repository PackmindHub/packmind (308 stars, last pushed today), licensed Apache-2.0. It adds 216 tokens to every session, about $0.0011 per session on Opus 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.