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 Kilo-Org/kilo-marketplace --skill oleander-iceberg-cataloggit clone --depth 1 https://github.com/Kilo-Org/kilo-marketplaceWrote 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/kilo-org/kilo-marketplace/oleander-iceberg-catalog)<a href="https://agentmods.dev/skills/kilo-org/kilo-marketplace/oleander-iceberg-catalog"><img src="https://agentmods.dev/badge/skills/kilo-org/kilo-marketplace/oleander-iceberg-catalog/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/kilo-org/kilo-marketplace/oleander-iceberg-catalog"><img src="https://agentmods.dev/badge/skills/kilo-org/kilo-marketplace/oleander-iceberg-catalog.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 17 findings, up to critical
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- critical Prompt Injection · line 2 This content may contain harmful instructions that could cause physical harm if followed. CRITICAL: Review carefully before use.Fix: Remove all content that could lead to harmful outcomes. Add safety guardrails and human oversight for any high-risk operations.
- critical Prompt Injection · line 4 This content may contain harmful instructions that could cause physical harm if followed. CRITICAL: Review carefully before use.Fix: Remove all content that could lead to harmful outcomes. Add safety guardrails and human oversight for any high-risk operations.
- critical Prompt Injection · line 10 This content may contain harmful instructions that could cause physical harm if followed. CRITICAL: Review carefully before use.Fix: Remove all content that could lead to harmful outcomes. Add safety guardrails and human oversight for any high-risk operations.
- critical Prompt Injection · line 15 This content may contain harmful instructions that could cause physical harm if followed. CRITICAL: Review carefully before use.Fix: Remove all content that could lead to harmful outcomes. Add safety guardrails and human oversight for any high-risk operations.
- critical Prompt Injection · line 17 This content may contain harmful instructions that could cause physical harm if followed. CRITICAL: Review carefully before use.Fix: Remove all content that could lead to harmful outcomes. Add safety guardrails and human oversight for any high-risk operations.
- critical Prompt Injection · line 23 This content may contain harmful instructions that could cause physical harm if followed. CRITICAL: Review carefully before use.Fix: Remove all content that could lead to harmful outcomes. Add safety guardrails and human oversight for any high-risk operations.
- critical Prompt Injection · line 27 This content may contain harmful instructions that could cause physical harm if followed. CRITICAL: Review carefully before use.Fix: Remove all content that could lead to harmful outcomes. Add safety guardrails and human oversight for any high-risk operations.
- critical Prompt Injection · line 32 This content may contain harmful instructions that could cause physical harm if followed. CRITICAL: Review carefully before use.Fix: Remove all content that could lead to harmful outcomes. Add safety guardrails and human oversight for any high-risk operations.
- critical Prompt Injection · line 33 This content may contain harmful instructions that could cause physical harm if followed. CRITICAL: Review carefully before use.Fix: Remove all content that could lead to harmful outcomes. Add safety guardrails and human oversight for any high-risk operations.
- critical Prompt Injection · line 34 This content may contain harmful instructions that could cause physical harm if followed. CRITICAL: Review carefully before use.Fix: Remove all content that could lead to harmful outcomes. Add safety guardrails and human oversight for any high-risk operations.
- critical Prompt Injection · line 42 This content may contain harmful instructions that could cause physical harm if followed. CRITICAL: Review carefully before use.Fix: Remove all content that could lead to harmful outcomes. Add safety guardrails and human oversight for any high-risk operations.
- critical Prompt Injection · line 52 This content may contain harmful instructions that could cause physical harm if followed. CRITICAL: Review carefully before use.Fix: Remove all content that could lead to harmful outcomes. Add safety guardrails and human oversight for any high-risk operations.
- critical Prompt Injection · line 58 This content may contain harmful instructions that could cause physical harm if followed. CRITICAL: Review carefully before use.Fix: Remove all content that could lead to harmful outcomes. Add safety guardrails and human oversight for any high-risk operations.
- critical Prompt Injection · line 77 This content may contain harmful instructions that could cause physical harm if followed. CRITICAL: Review carefully before use.Fix: Remove all content that could lead to harmful outcomes. Add safety guardrails and human oversight for any high-risk operations.
- critical Prompt Injection · line 88 This content may contain harmful instructions that could cause physical harm if followed. CRITICAL: Review carefully before use.Fix: Remove all content that could lead to harmful outcomes. Add safety guardrails and human oversight for any high-risk operations.
- critical Prompt Injection · line 89 This content may contain harmful instructions that could cause physical harm if followed. CRITICAL: Review carefully before use.Fix: Remove all content that could lead to harmful outcomes. Add safety guardrails and human oversight for any high-risk operations.
- critical Prompt Injection · line 107 This content may contain harmful instructions that could cause physical harm if followed. CRITICAL: Review carefully before use.Fix: Remove all content that could lead to harmful outcomes. Add safety guardrails and human oversight for any high-risk operations.
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.00755 |
| Opus 5 | $0.00017 | $0.00378 |
| Sonnet 5 | $0.00007 | $0.00151 |
| Haiku 4.5 | $0.00003 | $0.00076 |
Grade A, and why
oleander-iceberg-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 9d 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
oleander Iceberg Catalog
Use this skill when reading from or writing to the oleander Iceberg catalog in a Spark job.
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).
Examples:
oleander.default.sf_311
oleander.san_francisco.district_stats
oleander.my_namespace.results
Reading tables
Use spark.table() with the fully qualified name:
df = spark.table("oleander.default.sf_311")
Never construct table paths as raw S3 URIs. Always use the catalog name so Iceberg metadata and lineage are tracked correctly.
Writing tables
Append (add rows to an existing or new table):
df.writeTo("oleander.my_namespace.my_table").append()
Overwrite (replace table contents):
df.write.mode("overwrite").saveAsTable("oleander.my_namespace.my_table")
Use writeTo(...).append() for incremental pipelines. Use write.mode("overwrite").saveAsTable(...) when replacing full result sets each run.
Prefer Spark writes over driver writes
Avoid collecting data to the driver and then writing from Python memory. Keep writes as Spark DataFrame operations so Iceberg handles the transaction, partitioning, and metadata correctly.
Bad:
rows = df.collect()
# write rows from Python memory
Good:
df.write.mode("overwrite").saveAsTable("oleander.my_namespace.my_table")
Parameterize table names
Accept table names as arguments or environment variables so scripts are reusable:
import os, argparse
parser = argparse.ArgumentParser()
parser.add_argument("--input-table", default="oleander.default.sf_311")
parser.add_argument("--output-catalog", default="oleander.my_namespace")
args = parser.parse_args()
df = spark.table(args.input_table)
df.write.mode("overwrite").saveAsTable(f"{args.output_catalog}.results")
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.
- 9d ago First seen · 114 lines · 34 tokens per session scan A 867035979dce
oleander-iceberg-catalog is a skill published in the GitHub repository Kilo-Org/kilo-marketplace (175 stars, last pushed 22d ago), licensed Apache-2.0. It adds 34 tokens to every session and 755 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-09-03.
Other skills, from other repositories
agent-platform-rag-engine-management
Manage and query Agent Platform RAG Engine Corpora and retrieve grounded contexts using the Google GenAI SDK. Use when listing RAG corpora or files, inspecting a corpus, retrieving contexts, or generating content grounded in a RAG corpus. Do not use for standard database queries (use SQL/Spanner skills), Google…
agent-platform-model-registry
Agent Platform Model Registry Management. Use when you need to upload, list, describe, update, or delete machine learning models (and their versions) in the Agent Platform Model Registry. Don't use for model training, model deployment to endpoints, or managing non-Agent Platform models.
foundry-config-setup
Resolve missing setup caused by a hardcoded Foundry project endpoint or model in a sample. Use when a sample fails because it uses a placeholder/hardcoded projectendpoint (for example "https://your-project.services.ai.azure.com") or a hardcoded model instead of reading them from the environment.
google-cloud-solution-agentic-analytics-spark-knowledge-catalog
Discovers requirements and generates guidance to design and deploy a governed, secure agentic-analytics solution for data that's distributed across Google Cloud, other cloud providers, or on-premises. Data that's outside Google Cloud (such as data from Databricks, Snowflake, Salesforce, SAP, or Oracle systems) is…
training-check
Interactively monitor training metrics from the current Codex session, periodically checking WandB or fallback logs for NaN, divergence, plateaus, and broken runs.
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.