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 Nevaberry/nevaberry-plugins --skill apache-iceberg-knowledge-patchgit clone --depth 1 https://github.com/Nevaberry/nevaberry-pluginsWrote 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/nevaberry/nevaberry-plugins/apache-iceberg-knowledge-patch)<a href="https://agentmods.dev/skills/nevaberry/nevaberry-plugins/apache-iceberg-knowledge-patch"><img src="https://agentmods.dev/badge/skills/nevaberry/nevaberry-plugins/apache-iceberg-knowledge-patch/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/nevaberry/nevaberry-plugins/apache-iceberg-knowledge-patch"><img src="https://agentmods.dev/badge/skills/nevaberry/nevaberry-plugins/apache-iceberg-knowledge-patch.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.00012 | $0.02172 |
| Opus 5.5 | $0.00005 | $0.00869 |
| Sonnet 5.5 | $0.00002 | $0.00434 |
| Haiku 4.5 | $0.00001 | $0.00217 |
Grade A, and why
apache-iceberg-knowledge-patch 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 1mo 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 — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Apache Iceberg Knowledge Patch
Use this skill when implementing, reviewing, upgrading, or operating Apache Iceberg tables and integrations. Start from the project's pinned Iceberg, engine, and table-format versions. Treat manifests, metadata JSON, catalog configuration, code, and tests as the authority for the deployment in front of you.
How to use this skill
- Identify the Iceberg library/runtime version, engine version, catalog type, file formats, and table format version.
- Read the compatibility and runtime notes before changing dependencies.
- Select the reference for the subsystem being changed.
- Check cross-cutting effects: format-v3 lineage and deletion vectors affect readers, rewrites, statistics, and cleanup; encryption affects metadata and file I/O; remote planning affects REST authorization and credentials.
- Preserve the existing table's format and operational invariants unless the task explicitly includes a migration.
- Verify behavior with the actual engine and catalog combination. Features in core are not automatically supported by every Spark, Flink, REST, or file- format path.
Reference index
| Reference | Topics |
|---|---|
| compatibility-and-runtime.md | Java, Spark, Flink, Hadoop, Hive, removed artifacts, API caveats |
| table-format-types-and-schema.md | Format v3/v4, row lineage, deletion vectors, Variant, geo, defaults, schema semantics |
| catalog-rest-and-security.md | REST protocol, scan planning, catalogs, authentication, encryption, cloud credentials |
| spark.md | Spark procedures, rewrites, metadata columns, streaming, migration, Variant |
| flink-kafka-and-streaming.md | Flink sources/sinks and maintenance, Kafka Connect ingestion |
| storage-formats-and-io.md | Parquet, Avro, ORC, Arrow, file-format registry, ADLS and object-store I/O |
| maintenance-statistics-and-rewrites.md | Expiration, partition/content statistics, rewrite planning, events and metrics |
What ships with it
8 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.
- coverage.json 731 B
- references/catalog-rest-and-security.md 5.7 KB
- references/compatibility-and-runtime.md 2.3 KB
- references/flink-kafka-and-streaming.md 3.0 KB
- references/maintenance-statistics-and-rewrites.md 4.5 KB
- references/spark.md 4.2 KB
- references/storage-formats-and-io.md 3.9 KB
- references/table-format-types-and-schema.md 5.0 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.
- 1mo ago First seen · 209 lines · 12 tokens per session scan A bc724d01fe52
apache-iceberg-knowledge-patch is a skill published in the GitHub repository Nevaberry/nevaberry-plugins (23 stars, last pushed 1mo ago), licensed MIT. It adds 12 tokens to every session and 2,172 once invoked, about $0.0000 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-30.
Other skills, from other repositories
api-canvas
DataCanvas primitive reference — a Tier 3 SQL/analytical workspace for tabular MCP servers, backed by DuckDB. Use when registering tables from upstream APIs, running ad-hoc SQL across them, and exporting results. Covers the acquire → register → query → export flow, per-table TTL, the token-sharing pattern for…
api-mirror
Stand up a persistent, self-refreshing local mirror of a bulk upstream dataset with the MirrorService (@cyanheads/mcp-ts-core/mirror). Use when a server wraps a large or slow API and should query a synced local index (embedded SQLite + FTS5) instead of paginating the live API per request.
redteam-sqli-detail-pack
Domain routing and boundary guidance for authorized SQL injection testing, including union-based, blind, error-based, stacked query, and second-order SQL injection variants. Use when a task belongs to the SQL injection domain and needs scope, evidence, pivot, or exit criteria.
design-mcp-server
Design the tool surface, resources, and service layer for a new MCP server. Use when starting a new server, planning a major feature expansion, or when the user describes a domain/API they want to expose via MCP. Produces a design doc at docs/design.md that drives implementation.
api-telemetry
Catalog of OpenTelemetry instrumentation built into framework @cyanheads/mcp-ts-core — spans, metrics, completion logs, env config, runtime caveats, custom instrumentation patterns, and cardinality rules. Use when enabling OTel export, adding custom spans or metrics in services, debugging missing telemetry, looking up…
maintenance
Investigate, adopt, and verify dependency updates — with special handling for @cyanheads/mcp-ts-core. Captures what changed, understands why, cross-references against the codebase, adopts framework improvements, syncs project skills, and runs final checks. Supports two entry modes: run the full flow end-to-end, or…