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 j4flmao/agent-skills --skill data-lakegit clone --depth 1 https://github.com/j4flmao/agent-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/j4flmao/agent-skills/data-lake)<a href="https://agentmods.dev/skills/j4flmao/agent-skills/data-lake"><img src="https://agentmods.dev/badge/skills/j4flmao/agent-skills/data-lake/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/j4flmao/agent-skills/data-lake"><img src="https://agentmods.dev/badge/skills/j4flmao/agent-skills/data-lake.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00101 | $0.04983 |
| Opus 5 | $0.00051 | $0.02491 |
| Sonnet 5 | $0.00020 | $0.00997 |
| Haiku 4.5 | $0.00010 | $0.00498 |
Grade A, and why
data-data-lake 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 8d 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 — 578 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Data Lake
Purpose
Design and operate ACID-compliant data lakes on object storage using Delta Lake, Apache Iceberg, or Apache Hudi. Manage table formats, optimize storage layout, enforce schema evolution, and implement time-travel and CDC patterns.
Agent Protocol
Trigger
Exact user phrases: "Delta Lake", "Apache Iceberg", "Apache Hudi", "Lakehouse", "ACID on lake", "time travel", "table format", "compaction", "Z-order", "Hilbert curve", "vacuum", "CDC", "merge-on-read", "copy-on-write", "manifest file", "metadata layer", "schema evolution", "optimize table", "incremental query".
Input Context
Before activating, verify:
- Object storage backend (S3, ADLS, GCS, MinIO)
- Table format preference (Delta, Iceberg, Hudi)
- Compute engine (Spark, Flink, Trino, Presto, Hive)
- Write pattern (append-heavy, update-heavy, CDC stream)
- Query pattern (OLAP, incremental, point lookup, full scan)
- Partition strategy (date, categorical, Z-order dimensions)
Output Artifact
Lake architecture with table format selection, compaction strategy, optimization plan.
Response Format
Table Format: {Delta Lake | Apache Iceberg | Apache Hudi}
Storage: {S3 | ADLS | GCS | MinIO}
Write Mode: {copy-on-write | merge-on-read}
Partition: {column, granularity}
Optimize: {Z-order by columns, compaction interval}
Vacuum: {retention hours}
-- DDL / optimization commands
No preamble. No postamble. No explanations. No filler/hedging/transitions. Compress output — why use many token when few do trick.
Completion Criteria
- Table format selected with trade-off analysis
- ACID guarantees documented (concurrent readers/writers)
- Write mode (CoW vs MoR) selected per table
- Partition strategy defined
- Compaction policy set (file size target, interval)
- Vacuum retention period configured
- Schema evolution rules defined
Max Response Length
250 lines of config.
Workflow
Step 1: Select Table Format
Format Comparison Matrix
What ships with it
32 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.
- references/api_reference.md 2.1 KB
- references/architecture_patterns.md 2.1 KB
- references/architecture-patterns.md 2.4 KB
- references/code-organization.md 1.9 KB
- references/configuration_guide.md 2.4 KB
- references/data-lake-advanced.md 2.4 KB
- references/data-lake-fundamentals.md 2.0 KB
- references/deployment_strategies.md 2.2 KB
- references/deployment-pipelines.md 2.1 KB
- references/error-handling.md 2.4 KB
- references/flink_state_management_1.md 2.2 KB
- references/flink_state_management_2.md 2.5 KB
- references/flink_state_management_3.md 2.2 KB
- references/flink_state_management_4.md 2.1 KB
- references/flink_state_management_5.md 2.2 KB
- references/flink_state_management_6.md 2.2 KB
- references/flink_state_management_7.md 2.1 KB
- references/flink_state_management_8.md 1.9 KB
- references/integration_guide.md 2.4 KB
- references/lake-gov-access.md 2.0 KB
- references/lake-operations.md 2.3 KB
- references/lake-performance-tuning.md 2.5 KB
- references/nessie-catalog.md 2.1 KB
- references/performance_tuning.md 2.1 KB
- references/performance-optimization.md 2.1 KB
- references/security_best_practices.md 2.5 KB
- references/security-best-practices.md 2.5 KB
- references/state-management.md 1.9 KB
- references/table-formats.md 1.8 KB
- references/testing-strategies.md 2.4 KB
- references/troubleshooting_guide.md 2.0 KB
- references/xtable-multi-format.md 2.1 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.
- 8d ago First seen · 578 lines · 101 tokens per session scan A 73b5658225f6
data-data-lake is a skill published in the GitHub repository j4flmao/agent-skills (23 stars, last pushed 6d ago), licensed MIT. It adds 101 tokens to every session and 4,983 once invoked, about $0.0005 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-09-03.
Other skills, from other repositories
build-with-tinybase
Scaffold, extend, and verify reactive local-first JavaScript or TypeScript applications with TinyBase. Use when choosing TinyBase for in-memory tabular or key-value state, generating an app with create-tinybase, adding schemas or UI bindings, configuring browser or database persistence, configuring MergeableStore…
api-reference
Memoria REST API endpoints, request/response formats, auth, rate limits. Use when calling or implementing API endpoints.
architecture
Memoria codebase structure, workspace layout, key traits, database tables, config patterns, and testing conventions. Use when navigating or modifying Memoria code.
deployment
Deploy Memoria with Docker Compose or Kubernetes. Environment variables, multi-instance setup, security. Use when deploying or configuring Memoria.
setup
Install Memoria and configure MCP for AI tools (Kiro, Cursor, Claude Code, Codex, Gemini CLI). Decision tree for Cloud vs self-hosted mode, database, embedding provider. Use when helping users set up Memoria.
plugin-development
Create, test, sign, and publish Memoria governance plugins. Covers Rhai and gRPC runtimes, manifest format, lifecycle. Use when developing or managing plugins.