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 skills/pedromneto97/custom-skills/sea-ormnpx skills add pedromneto97/custom-skills --skill sea-ormgit clone --depth 1 https://github.com/pedromneto97/custom-skillsWrote 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/skills/pedromneto97/custom-skills/sea-orm)<a href="https://agentmods.dev/skills/pedromneto97/custom-skills/sea-orm"><img src="https://agentmods.dev/badge/skills/pedromneto97/custom-skills/sea-orm.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.00110 | $0.00812 |
| Opus 5 | $0.00055 | $0.00406 |
| Sonnet 5 | $0.00022 | $0.00162 |
| Haiku 4.5 | $0.00011 | $0.00081 |
Grade A, and why
sea-orm 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 6d 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SeaORM v2 — Skill Index
Covers sea-orm 2.0.0-rc (open-source) and SeaORM-X (MSSQL commercial). Load only the reference file(s) relevant to the task. Do not load all files at once.
Reference files
| Topic | File |
|---|---|
Cargo.toml dependencies, feature flags, workspace setup |
reference/01-cargo-setup.md |
Database::connect, ConnectOptions, pool, ping |
reference/02-connection.md |
Migrations — CLI, file layout, MigratorTrait, DDL helpers, raw SQL, seed data |
reference/03-migrations.md |
| Entity structure — dense vs compact, attributes, CLI codegen, Rust↔DB type map | reference/04-entity-structure.md |
CRUD Insert — insert one/many, exec_with_returning, on-conflict, IDENTITY_INSERT |
reference/05-crud-insert.md |
| CRUD Select — find, filter, COLUMN constants, relations, pagination, partial model | reference/06-crud-select.md |
CRUD Update & Delete — update one/many, delete one/many, exec_with_returning |
reference/07-crud-update-delete.md |
| MSSQL-specific — savepoints, IDENTITY_INSERT, OUTPUT, schema rewrite, tuple IN | reference/08-mssql-features.md |
| v1 → v2 breaking changes | reference/09-v1-v2-migration.md |
| Repository boundary patterns — mappers, transactions, infra→domain error mapping | reference/10-repository-patterns.md |
Quick decision guide
- Starting a new project? → load
01-cargo-setup.md+02-connection.md+03-migrations.md - Defining entities? → load
04-entity-structure.md - Writing queries? → load the relevant CRUD file(s):
05,06, or07 - Implementing repositories? → load
10-repository-patterns.md(+ relevant CRUD file) - Using MSSQL / SeaORM-X? → always also load
08-mssql-features.md - Upgrading from v1? → load
09-v1-v2-migration.md
Key v2 concepts (quick reference)
- Use
#[sea_orm::model](dense format) to unlockCOLUMNconstants, autofind_by_*/delete_by_*,ModelEx, and Entity Loader. exec_with_returningis supported on INSERT, UPDATE, and DELETE for Postgres, SQLite, and MSSQL.- M-N
load_manyno longer requires a junction entity in v2. - MSSQL
IDENTITY_INSERTis handled automatically by SeaORM-X when a PK column isSet(...). currentSchemain the MSSQL connection string auto-prefixes all queries — no explicit schema annotations needed.
What ships with it
10 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- reference/01-cargo-setup.md 1.6 KB
- reference/02-connection.md 1.9 KB
- reference/03-migrations.md 6.1 KB
- reference/04-entity-structure.md 4.6 KB
- reference/05-crud-insert.md 4.3 KB
- reference/06-crud-select.md 4.5 KB
- reference/07-crud-update-delete.md 2.0 KB
- reference/08-mssql-features.md 2.2 KB
- reference/09-v1-v2-migration.md 1.1 KB
- reference/10-repository-patterns.md 2.5 KB
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.
- 6d ago First seen · 48 lines · 110 tokens per session scan A 5201e24f1fdc
sea-orm is a skill published in the GitHub repository pedromneto97/custom-skills (2 stars, last pushed 2mo ago), licensed MIT. It adds 110 tokens to every session and 812 once invoked, about $0.0006 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-31.
Other skills, from other repositories
encore-go-database
Work with PostgreSQL in Encore Go using sqldb.NewDatabase from encore.dev/storage/sqldb — schema migrations and SQL queries.
golem-add-postgres-rust
Using golem:rdbms/postgres from a Rust Golem agent. Use when the user asks to connect to PostgreSQL, run SQL, execute a Postgres transaction, or use PostgreSQL from Rust agent code.
creating-oracle-to-postgres-master-migration-plan
Discovers all projects in a .NET solution, classifies each for Oracle-to-PostgreSQL migration eligibility, and produces a persistent master migration plan. Use when starting a multi-project Oracle-to-PostgreSQL migration, creating a migration inventory, or assessing which .NET projects contain Oracle dependencies.
cli-forge-data
Design and implement safe PostgreSQL database changes for Rust/SQLx applications. Use for new schemas, migrations, constraints, indexes, repositories, transaction boundaries, state machines, idempotency, concurrency control, queues, multi-tenancy, soft deletion, ledgers, outbox/inbox, repair jobs, or corrections…
rc-sqlx
Implements and reviews SQLx 0.8+ with PostgreSQL in Rust — PgPool, query/queryas, bind parameters, transactions, migrations, compile-time macros, database tests. Use when writing or changing SQLx/Postgres access from Rust. Do not use for Axum routing alone (rc-axum), SvelteKit (rc-sveltekit), Rust idioms (rc-rust), or…
drizzle-orm
Expert knowledge for Drizzle ORM - the lightweight, type-safe SQL ORM for edge and serverlessUse when "drizzle, drizzle orm, drizzle-kit, drizzle schema, drizzle migration, drizzle relations, sql orm typescript, edge database, d1 database, orm, database, typescript, sql, edge, serverless, d1, postgres, mysql, sqlite"…