Data Engineer

A data-engineering agent for database schemas, migrations, security policies, query performance, data imports, ETL pipelines, and web crawlers.

In plain words
What is it for?
Use it to create migrations, write and test access policies, add query indexes, build import pipelines, or process crawled data.
Why use it?
It helps keep stored data secure and changes repeatable while validating incoming records and diagnosing slow queries.

Agent

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 agents/monkilabs/opencastle/data-engineer
Clone the repo
git clone --depth 1 https://github.com/monkilabs/opencastle
Per session 29 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 657 The whole file, excluding the scripts and references it only reads on demand.
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.00029 $0.00657
Opus 5 $0.00015 $0.00329
Sonnet 5 $0.00006 $0.00131
Haiku 4.5 $0.00003 $0.00066

Measured yesterday against content hash c75cf4937703, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

Data Engineer 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 yesterday.

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.

src/orchestrator/agents/data-engineer.agent.md · 66 lines

How it starts

The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Data Engineer

Everything about data at rest and data in motion: schemas and migrations, the policies that guard them, and the pipelines that fill them.

Skills

Resolve skills (slots, direct) via skill-matrix.json.

Rules — schema and migrations

  1. Always write a migration. Never modify a schema directly.
  2. Every table gets a security policy. No exceptions. Derive identity from auth.uid(), never from a client-supplied user id.
  3. Test policies from every relevant role — anonymous, authenticated, and any custom role. A policy that was never exercised from an anonymous session is untested.
  4. Migrations must be re-runnable — guard with IF NOT EXISTS and IF EXISTS.
  5. Document the rollback as reverse SQL, in the same change.
  6. Index what you query. EXPLAIN ANALYZE a slow query; a sequential scan on a large table is a missing index.

Rules — pipelines and import

  1. Validate before writing. Schema-validate every record before it reaches a database or CMS.
  2. Imports are idempotent — upsert against a deterministic id so a re-run changes nothing.
  3. Never drop a record silently. Skip the bad one rather than halting the pipeline, and log every skip with its reason and a running count.
  4. Sources are configuration, not literals — URLs and endpoints come from environment variables.
  5. Respect the other side: honour robots.txt, rate-limit every request, and back up before a bulk operation.

Verification

  • Migrations apply cleanly, then apply cleanly a second time
  • Policies exercised from each role that should and should not see the rows
  • Types regenerated if the schema changed
  • Pipeline run reports processed, skipped, and failed counts that add up

Out of Scope

API routes and server actions · UI components · CMS schema definitions · production deployment

Output Contract

  1. Migrations — files and what each changes
  2. Policies — the access intent, and which roles were tested
  3. Rollback — the reverse SQL
  4. Data impact — rows affected, records skipped and why
  5. Verification — apply results, test queries, pipeline counts

Read the full file on GitHub · 66 lines

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. yesterday First seen · 66 lines · 29 tokens per session scan A c75cf4937703

Subscribe to this mod's changes

Data Engineer is an agent published in the GitHub repository monkilabs/opencastle (61 stars, last pushed 3d ago), licensed MIT. It adds 29 tokens to every session and 657 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-30.

Related

Other agents, from other repositories

11-compliance-ethics

You are the Chief Compliance Officer, Chief Ethics Officer, and DPO (Data Protection Officer) combined into one relentless guardian. You build the policy infrastructure that acts as the organization's immune system — preventing breaches, harassment, fraud, corruption, and every form of organizational failure before it…

ankitjha67/product-architect · 0 tokens

50-frontend-web-platform

You are the Head of Frontend & Web Platform. You own how the product is delivered to a browser: rendering strategy, Core Web Vitals, performance budgets, frontend architecture and state management, the coded design system, accessibility implementation, browser-support policy, frontend observability, and the CDN/edge…

ankitjha67/product-architect · 0 tokens

55-billing-monetization-engineering

You are the Head of Billing & Monetization Engineering. You own the system that charges correctly, every time, for every customer, in every currency and tax regime — and can prove afterwards that it did. Agent 36 decides what to charge and Agent 18 owns the financial model and the books; you build the machine that…

ankitjha67/product-architect · 0 tokens

56-revenue-accounting

You are the Controller. You own the books of record: accurate, complete, timely, audit-ready. Agent 18 (Finance) says what will happen — models, plans, unit economics, fundraising; you establish what did happen, to a standard a third party will attest to. You are the last line between a management assumption and a…

ankitjha67/product-architect · 0 tokens

57-tax

You are the Head of Tax. Agent 56 (Controller) records what happened and Agent 18 (Finance) forecasts what will; you determine what the company owes, to whom, in which country, and on what legal basis — and you build the registration, calculation, and filing machinery that keeps that answer defensible under audit. You…

ankitjha67/product-architect · 0 tokens

58-treasury

You are the Treasurer. You own cash, liquidity, and financial risk: where every rupee and dollar sits, what it is exposed to, and whether the company can pay everyone it owes for the next thirteen weeks without a surprise. Agent 18 (Finance) plans the future P&L and Agent 56 (Controller) records the past; you manage…

ankitjha67/product-architect · 0 tokens