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/adelie-squad/solosquad/data-engineernpx skills add Adelie-Squad/solosquad --skill data-engineergit clone --depth 1 https://github.com/Adelie-Squad/solosquadWrote 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/adelie-squad/solosquad/data-engineer)<a href="https://agentmods.dev/skills/adelie-squad/solosquad/data-engineer"><img src="https://agentmods.dev/badge/skills/adelie-squad/solosquad/data-engineer.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.00037 | $0.00539 |
| Opus 5 | $0.00018 | $0.00269 |
| Sonnet 5 | $0.00007 | $0.00108 |
| Haiku 4.5 | $0.00004 | $0.00054 |
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 3d 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 Engineer — v1.1 (merged)
R&R
담당 범위 (구 data-collector)
- 외부 데이터 수집 (scrape / API ingestion)
- 데이터 schema 정의
- raw data 저장
담당 범위 (구 data-engineer)
- ETL / ELT 파이프라인
- warehouse 설계 (dbt, BigQuery, etc.)
- 데이터 quality 모니터링
- backfill / replay 처리
담당하지 않는 것
- 분석 / KPI → product/data-analyst
- 데이터 정책 / 규제 → product-designer
v1.1 병합 노트
수집 (scrape/ETL) + 파이프라인 (warehouse) 은 동일 데이터 lifecycle. 분리 시 handoff cost 큼.
HARD GATE
- [ ] data quality check 통과 (null/dup/schema)
- [ ] product-designer 검토 (PII / GDPR / PIPA)
- [ ] ≥ 2 approaches (e.g. batch vs streaming, push vs pull)
- [ ] backfill plan 명시 (idempotent 보장)
Reference
- 이전:
assets/agents/engineering/{data-collector, data-engineer}/SKILL.md - v1.1 PRD §8.1 (병합)
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.
- 3d ago First seen · 71 lines · 37 tokens per session scan A 7d50c13421ed
data-engineer is a skill published in the GitHub repository Adelie-Squad/solosquad (19 stars, last pushed 13d ago), licensed MIT. It adds 37 tokens to every session and 539 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-08-30.
Other skills, from other repositories
alloydb-basics
Manages clusters, instances, and backups for AlloyDB for PostgreSQL, and integrates with AlloyDB Model Context Protocol (MCP) tools for automated database operations. Use when creating, configuring, or administering AlloyDB databases. Do NOT use for general PostgreSQL instances (e.g. Cloud SQL) or other GCP databases.
cognee-community
Use when the user needs something that ships outside cognee core — community database adapters (Qdrant, Milvus, Weaviate, Redis, Pinecone, FalkorDB, Memgraph, DuckDB, NetworkX, …), data-source connectors (Slack, Gmail, Notion, Confluence, Google Drive), custom tasks/pipelines/retrievers (Exa, ScrapeGraph, codify)…
lineage-diff
Compare column-level lineage between two versions of a SQL query to show added, removed, and changed data flow edges.
django-migrations
Django migration patterns and safety workflow for PostHog. Use when creating, adjusting, or reviewing Django/Postgres migrations, including non-blocking index/constraint changes, multi-phase schema changes, data backfills, migration conflict rebasing, and product model moves that require SeparateDatabaseAndState. Also…
digoal
Portable digital employee distilled from digoal's personal blog for PostgreSQL, PolarDB, DuckDB, AI+database, vector/RAG, database operations, source-code reading, technical content creation, open-source community strategy, and "德说" style strategic analysis. Use when asked to answer as 德哥/digoal, mine a local…
aliyun-opensearch-search
Use when working with OpenSearch vector search edition via the Python SDK (ha3engine) to push documents and run HA/SQL searches. Ideal for RAG and vector retrieval pipelines in Claude Code/Codex.