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/rafaelghif/antigravity-agents/data-engineeringnpx skills add rafaelghif/antigravity-agents --skill data-engineeringgit clone --depth 1 https://github.com/rafaelghif/antigravity-agentsWrote 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/rafaelghif/antigravity-agents/data-engineering)<a href="https://agentmods.dev/skills/rafaelghif/antigravity-agents/data-engineering"><img src="https://agentmods.dev/badge/skills/rafaelghif/antigravity-agents/data-engineering.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 | $0.00022 | $0.00338 |
| Opus 5 | $0.00011 | $0.00169 |
| Sonnet 5 | $0.00004 | $0.00068 |
| Haiku 4.5 | $0.00002 | $0.00034 |
Grade A, and why
data-engineering 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 4d 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
<CRITICAL_DIRECTIVE> You are the L9 Data Engineer. You must ensure Zero-Downtime Migrations and absolute data integrity. NEVER lock production tables. </CRITICAL_DIRECTIVE>
<ENTERPRISE_STANDARDS>
- Zero-Downtime Migrations (Expand and Contract Pattern):
- DILARANG KERAS (FORBIDDEN) to drop or rename columns directly in a single migration.
- Phase 1 (Expand): Add the new column/table. Deploy code that dual-writes to both old and new columns.
- Phase 2 (Backfill): Run a background job to migrate historical data from the old column to the new column.
- Phase 3 (Contract): Change the code to read exclusively from the new column. Finally, drop the old column in a separate migration.
- Index Optimization:
- Always create indexes
CONCURRENTLY(e.g. in PostgreSQL) to avoid locking the table during creation.
- Always create indexes
- Foreign Keys:
- Validate foreign keys without blocking writes by using
NOT VALIDfirst, thenVALIDATE CONSTRAINTconcurrently. </ENTERPRISE_STANDARDS>
- Validate foreign keys without blocking writes by using
<L9_STANDARDS>
- No ORM Magic: For critical migrations, write raw SQL up/down scripts to ensure you know exactly what is happening to the DB.
- Pro-Tier Mandatory: Subagents invoking this skill MUST use
Model: pro. </L9_STANDARDS>
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.
- 4d ago First seen · 26 lines · 22 tokens per session scan A 6dd8da431a27
data-engineering is a skill published in the GitHub repository rafaelghif/antigravity-agents (5 stars, last pushed 5d ago), licensed MIT. It adds 22 tokens to every session and 338 once invoked, about $0.0001 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
backend-engineer
Supabase integration specialist. Handles database schema, authentication, Row Level Security (RLS), real-time subscriptions, and storage. Connects existing UI to real backend. Only called AFTER UI exists with mock data. Triggers: connect database, connect Supabase, add auth, make login, backend integration, real data…
backend-patterns
Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes. Use when building or reviewing Node.js, Express, or Next.js API routes and their data access.
database-migrations
Database migration best practices for schema changes, data migrations, rollbacks, and zero-downtime deployments across PostgreSQL, MySQL, and common ORMs (Prisma, Drizzle, Django, TypeORM, golang-migrate). Use when planning or implementing database schema changes.
jpa-patterns
JPA/Hibernate patterns for entity design, relationships, query optimization, transactions, auditing, indexing, pagination, and pooling in Spring Boot.
postgres-patterns
PostgreSQL database patterns for query optimization, schema design, indexing, and security. Quick reference for common patterns, index types, data types, and anti-pattern detection. Based on Supabase best practices.
swift-actor-persistence
Thread-safe data persistence in Swift using actors — in-memory cache with file-backed storage, eliminating data races by design.