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/nedcodes-ok/cursorrules-collectionWrote 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/nedcodes-ok/cursorrules-collection/sequelize)<a href="https://agentmods.dev/rules/nedcodes-ok/cursorrules-collection/sequelize"><img src="https://agentmods.dev/badge/rules/nedcodes-ok/cursorrules-collection/sequelize/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/nedcodes-ok/cursorrules-collection/sequelize"><img src="https://agentmods.dev/badge/rules/nedcodes-ok/cursorrules-collection/sequelize.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.00376 | $0.00376 |
| Opus 5.5 | $0.00150 | $0.00150 |
| Sonnet 5.5 | $0.00075 | $0.00075 |
| Haiku 4.5 | $0.00038 | $0.00038 |
Grade A, and why
sequelize 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
Sequelize Rules
Model Definition
- Use sequelize.define() or class-based models extending Model
- Define attributes with proper data types and validation rules
- Use underscored naming convention for database columns
- Implement proper indexes for performance-critical fields
- Define timestamps (createdAt, updatedAt) explicitly
Associations
- Define associations in model files or separate association files
- Use hasMany, hasOne, belongsTo, belongsToMany appropriately
- Always define foreign key constraints and onDelete/onUpdate actions
- Use include option for eager loading related data
- Implement through models for many-to-many relationships
Migrations
- Create migrations for all database schema changes
- Use descriptive migration filenames with timestamps
- Implement both up and down methods for rollback capability
- Add proper indexes in migrations, not just model definitions
- Use transactions in migrations for atomicity
Querying
- Use findOne, findAll, findByPk for basic queries
- Implement proper where clauses with operators (Op.eq, Op.like, etc.)
- Use attributes option to select specific fields
- Implement pagination with limit and offset
- Use raw queries sparingly and with proper parameter binding
Validation & Hooks
- Implement model-level validations for data integrity
- Use beforeSave, afterSave hooks for business logic
- Implement custom validation functions when needed
- Use paranoid models for soft deletes when appropriate
- Add proper error handling for validation failures
Performance
- Use connection pooling configuration
- Implement proper eager loading to avoid N+1 queries
- Use database transactions for complex operations
- Add database indexes for frequently queried fields
- Use read replicas for read-heavy operations
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 · 49 lines · 376 tokens per session scan A e0c04873a4ab
sequelize is a cursor rule published in the GitHub repository nedcodes-ok/cursorrules-collection (38 stars, last pushed 7mo ago), licensed MIT. It adds 376 tokens to every session, about $0.0015 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-09-03.
Other cursor rules, from other repositories
express
Express/Node.js best practices.
fastapi-file-structure
A recommended FastAPI project structure that separates routes, configuration, security, database sessions, create/read/update/delete operations, models, and schemas into modules.
java-springboot-jpa-cursorrules-prompt-file
Cursor rules for Java development with Springboot and JPA integration.
nodejs-mongodb-cursorrules-prompt-file-tutorial
Cursor rules for Node.js development with MongoDB integration.
repository-class-conventions
A set of rules for Spring Data repositories, which are interfaces that access application data. It specifies JpaRepository, JPQL queries, DTOs, and EntityGraph settings for related records.
tech-stack
A set of backend technology rules for Node.js and Express.js, using MongoDB with Mongoose for data storage. It also specifies JWT authentication, Git, and possible Docker deployment.