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 OleanderHQ/claude-plugin --skill lake-cataloggit clone --depth 1 https://github.com/OleanderHQ/claude-pluginWrote 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/oleanderhq/claude-plugin/lake-catalog)<a href="https://agentmods.dev/skills/oleanderhq/claude-plugin/lake-catalog"><img src="https://agentmods.dev/badge/skills/oleanderhq/claude-plugin/lake-catalog.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.1 | $0.00057 | $0.00590 |
| Opus 5 | $0.00028 | $0.00295 |
| Sonnet 5 | $0.00011 | $0.00118 |
| Haiku 4.5 | $0.00006 | $0.00059 |
Grade A, and why
lake-catalog 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
oleander Lake Catalog
Use this skill when reading from or writing to the oleander lake catalog from Spark, Polars, SQL, or another engine.
Catalog hierarchy
Tables are addressed as catalog.namespace.table:
- catalog: always
oleanderfor the managed Lakekeeper-backed catalog - namespace: a logical grouping (e.g.,
default,san_francisco,my_org) - table: the table name
By default, default and telemetry namespaces are available out of the box. The telemetry namespace contains oleander-managed data you can query directly (for example oleander.telemetry.run_events, oleander.telemetry.traces, and oleander.telemetry.logs).
These tables are partitioned on their time column and are reachable over MCP with query_run — see the lake-query skill.
Examples:
oleander.default.sf_311
oleander.san_francisco.district_stats
oleander.my_namespace.results
Referencing tables
Always use fully qualified table names through the engine's catalog integration. Do not build raw storage paths such as S3 URIs when reading or writing Iceberg tables.
Good patterns:
- read
oleander.default.sf_311through your engine's catalog-aware table API - write results to
oleander.my_namespace.results
Avoid:
- hardcoding storage locations like
s3://.../warehouse/... - bypassing the catalog when the engine supports catalog-qualified reads and writes
Using the catalog name keeps Iceberg metadata, lineage, and table semantics consistent across engines.
Engine-specific read/write syntax
This skill defines the shared catalog rules. Engine-specific syntax and operational advice should live in engine-specific skills.
Use companion skills when available:
- Spark: see
spark-lake-catalogforspark.table(...), write modes, and caching guidance - Other engines: keep the same table naming and catalog-reference rules, but use that engine's native API
Namespace conventions
- Use lowercase, underscore-separated names for namespaces and tables.
- Keep the namespace tied to the domain or data source, not the job name.
- Avoid deeply nested namespaces; one level is usually sufficient.
What ships with it
1 file 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.
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 · 70 lines · 57 tokens per session scan A 62bb211310aa
lake-catalog is a skill published in the GitHub repository OleanderHQ/claude-plugin (4 stars, last pushed 29d ago), licensed Apache-2.0. It adds 57 tokens to every session and 590 once invoked, about $0.0003 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
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for prisma-next. Use when the user wants to create a pull request, open a PR, or submit changes for review.
schema-exploration
Lists tables, describes columns and data types, identifies foreign key relationships, and maps entity relationships in a database. Use when the user asks about database schema, table structure, column types, what tables exist, ERD, foreign keys, or how entities relate.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
supabase
Supabase / PostgREST Row-Level-Security playbook — pull the anon (or leaked servicerole) key out of the frontend JS, map tables from the auto-generated OpenAPI spec, test anonymous RLS READ disclosures (PII/secret leaks), and anonymous RLS WRITE abuse (insert/update/delete — e.g. forging…
nornicdb-cypher-queries
Pick fast, predictable Cypher query shapes in NornicDB — point lookups, batch retrieval, pagination, search, traversal, batched UNWIND/MERGE writes, cleanup, multi-tenant isolation. Use when writing or reviewing Cypher whose latency or throughput matters; maps user intent to the executor's hot-path query templates.
dsql
Build with Aurora DSQL — manage schemas, execute queries, handle migrations, diagnose query plans, diagnose cluster performance, load data, and develop applications with a serverless, distributed SQL database. Covers IAM auth, multi-tenant patterns, MySQL-to-DSQL and PostgreSQL-to-DSQL schema conversion, foreign key…