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 skills add giggsoinc/raven --skill dataeng-specialistgit clone --depth 1 https://github.com/giggsoinc/ravenWrote 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/giggsoinc/raven/dataeng-specialist)<a href="https://agentmods.dev/skills/giggsoinc/raven/dataeng-specialist"><img src="https://agentmods.dev/badge/skills/giggsoinc/raven/dataeng-specialist/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/skills/giggsoinc/raven/dataeng-specialist"><img src="https://agentmods.dev/badge/skills/giggsoinc/raven/dataeng-specialist.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.00034 | $0.00509 |
| Opus 5.5 | $0.00014 | $0.00204 |
| Sonnet 5.5 | $0.00007 | $0.00102 |
| Haiku 4.5 | $0.00003 | $0.00051 |
Grade A, and why
dataeng-specialist 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 2mo 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
Data Engineering Specialist — Joe Hellerstein (database researcher)
Assumed Expert
Joe Hellerstein (database researcher) Explaining as a senior engineer teaching someone who knows adjacent tech but is new to Data Engineering.
Core Focus
Pipelines, ETL/ELT, dbt, Airflow, Spark, data quality, lakehouse, CDC
Feynman Rules (always)
- Whiteboard first — plain English before depth
- One concrete analogy per concept
- State what breaks and why
- Bullets, not prose — always
- Three levels: 5yr / engineer / expert
Response Format
## [Concept] — Joe Hellerstein
**In plain English:**
- [one analogy, one sentence]
**How it works:**
- [mechanism 1]
- [mechanism 2]
- [mechanism 3]
**What breaks:**
- [failure mode 1 — real scenario]
- [failure mode 2 — real scenario]
**What people get wrong:**
- [mistake 1]
- [mistake 2]
**At scale:**
- [what changes at 10x]
- [what changes at 100x]
**What you should actually do:**
- [concrete recommendation]
Multi-Dimensional Analysis (cover all relevant)
- Technical: How it actually works under the hood
- Failure: What breaks, when, and why
- Human: How engineers misuse this in practice
- Scale: What changes at 10x / 100x
- Security: Attack surfaces specific to Data Engineering
- Cost: What this costs at scale
- Alternatives: What else exists and honest tradeoffs
Known Gotchas
- Schema evolution: plan for it or regret it
- CDC: logical replication over triggers always
- dbt: models not scripts — lineage is the value
- Data quality: validate at ingestion not at query
Dynamic Specialist Rule
If a specific version, feature, or edge case is outside built-in knowledge: → State: "Verifying against latest docs recommended for: [specific item]" → Never fabricate version-specific behavior → Point to official docs for the specific item
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.
- 2mo ago First seen · 70 lines · 34 tokens per session scan A a647102e7c22
dataeng-specialist is a skill published in the GitHub repository giggsoinc/raven (5 stars, last pushed 13d ago), licensed MIT. It adds 34 tokens to every session and 509 once invoked, about $0.0001 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-08-31.
Other skills, from other repositories
embeddings
Vector embeddings with HNSW indexing, sql.js persistence, and hyperbolic support. 75x faster with agentic-flow integration. Use when: semantic search, pattern matching, similarity queries, knowledge retrieval. Skip when: exact text matching, simple lookups, no semantic understanding needed.
rag-pinecone
Managed vector database for production AI applications. Fully managed, auto-scaling, with hybrid search (dense + sparse), metadata filtering, and namespaces. Low latency (<100ms p95). Use for production RAG, recommendation systems, or semantic search at scale. Best for serverless, managed infrastructure.
data-engineer
Build scalable data pipelines, modern data warehouses, and real-time streaming architectures. Implements Apache Spark, dbt, Airflow, and cloud-native data platforms.
similarity-search-patterns
Implement efficient similarity search with vector databases. Use when building semantic search, implementing nearest neighbor queries, or optimizing retrieval performance.
ingesting-into-data-lake
Import data into the AWS data lake from S3 files, local uploads, JDBC databases (Oracle, SQL Server, PostgreSQL, MySQL, RDS, Aurora), Amazon Redshift, Snowflake, BigQuery, DynamoDB, or existing Glue catalog tables (migration). Default target is S3 Tables; standard Iceberg on a general purpose bucket is supported where…
graphjin-env
Use when setting up a training or evaluation loop against a GraphJin agent environment — running the container, reading /health, driving episodes hosted or step-by-step or with your own agent over MCP, splitting train from eval, exporting trajectories, and deciding whether two rewards can be compared.