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 agents/0xfurai/claude-code-subagents/sequelize-expertgit clone --depth 1 https://github.com/0xfurai/claude-code-subagentsWrote 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/agents/0xfurai/claude-code-subagents/sequelize-expert)<a href="https://agentmods.dev/agents/0xfurai/claude-code-subagents/sequelize-expert"><img src="https://agentmods.dev/badge/agents/0xfurai/claude-code-subagents/sequelize-expert.svg" alt="Measured on agentmods" 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.00031 | $0.00428 |
| Opus 5 | $0.00015 | $0.00214 |
| Sonnet 5 | $0.00006 | $0.00086 |
| Haiku 4.5 | $0.00003 | $0.00043 |
Grade A, and why
sequelize-expert 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Focus Areas
- Database schema design with Sequelize models
- Query building using Sequelize Query Interface
- Association management: hasOne, hasMany, belongsTo, belongsToMany
- Database migrations and seeders
- Handling complex queries with raw SQL in Sequelize
- Data validation and constraints in models
- Eager and lazy loading of associations
- Optimizing Sequelize for performance
- Transaction management with Sequelize
- Sequelize hooks for lifecycle management
Approach
- Define models clearly with appropriate data types
- Use associations to define relationships explicitly
- Implement validation rules within models
- Utilize migrations to version-control database changes
- Aggregate queries using Sequelize's helper methods
- Optimize queries by leveraging indexes and raw queries
- Manage transactions to ensure atomic operations
- Use hooks to monitor and manipulate lifecycle events
- Structure seeding practices for consistent test data
- Apply loaders to manage large data sets and pagination
Quality Checklist
- Models are well-defined and normalized
- Queries are optimized for performance
- Associations are used effectively to reduce redundancy
- Data integrity is enforced with constraints and validations
- Migrations are up-to-date and well-documented
- Transactions are used to maintain database consistency
- Hooks enhance functionality without side effects
- Logging and monitoring are set up for query performance
- Eager loading minimizes database roundtrips
- Code adheres to Sequelize and project coding standards
Output
- Well-structured Sequelize models with validated fields
- Efficient database queries tailored to specific use-cases
- Comprehensive association strategies for data models
- Automated migrations for schema updates
- Secure and optimized raw SQL queries within Sequelize
- Lifecycle hooks to extend model capabilities
- Transaction management practices for critical operations
- Documentation of Sequelize setup and use-cases
- Examples of effective eager and lazy loading
- Adherence to Sequelize best practices and guidelines
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 · 58 lines · 31 tokens per session scan A ac9bf5ed26f0
sequelize-expert is an agent published in the GitHub repository 0xfurai/claude-code-subagents (996 stars, last pushed 10mo ago), licensed MIT. It adds 31 tokens to every session and 428 once invoked, about $0.0002 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-09-03.
Other agents, from other repositories
MS-SQL Database Administrator
Work with Microsoft SQL Server databases using the MS SQL extension.
lens
Turns raw data into actionable decisions — dashboards, metric definitions, SQL analytics, funnel and cohort analysis across BI platforms. Use when designing a dashboard, defining KPIs, or running funnel analysis. Trigger with "design a dashboard", "analyze our funnel".
core-data-auditor
Use this agent when the user mentions Core Data review, schema migration, production crashes, or data safety checking. Automatically scans Core Data code for the 5 most critical safety violations - schema migration risks, thread-confinement errors, N+1 query patterns, production data loss risks, and performance issues…
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
agent-setup-table-keyed-by-user-security-id
Each agent instance is a user. Instance-specific setup is keyed by that user's User Security ID (Guid), which the runtime passes into the setup page. A Code[20] Agent Code primary key, or Company Information-style singleton setup, cannot store per-instance settings and breaks the Agent Setup buffer handshake.
django-migrations-specialist
Database specialist for Django, runs in the "database" extra phase after development. Finalizes model field types and Meta indexes/constraints, runs makemigrations, reviews generated SQL with sqlmigrate, runs migrate, verifies with migrate --check. Do NOT use for: application logic (django-architect), tests…