A skill for tracing where data comes from and where it flows in Collibra's technical lineage graph.

It finds upstream sources and downstream users of tables, files, code, and other data entities, and can retrieve transformation SQL or scripts when requested.

It separates physical data flow from business catalog links and prevents using the wrong kind of identifier when following a lineage path.

lineage — Skill for Claude Code and Codex by collibra/chip

Install

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.

Any agent

npx skills add collibra/chip --skill lineage

Clone the repo

git clone --depth 1 https://github.com/collibra/chip

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/collibra/chip/lineage/github.svg)](https://agentmods.dev/skills/collibra/chip/lineage)

Your own site

<a href="https://agentmods.dev/skills/collibra/chip/lineage"><img src="https://agentmods.dev/badge/skills/collibra/chip/lineage/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/collibra/chip/lineage"><img src="https://agentmods.dev/badge/skills/collibra/chip/lineage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 26 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 860 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

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.00026	$0.00860
Opus 5.5	$0.00010	$0.00344
Sonnet 5.5	$0.00005	$0.00172
Haiku 4.5	$0.00003	$0.00086

Measured 2mo ago against content hash 2038f393acae, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

lineage 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 2mo 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.

pkg/skills/files/collibra/lineage/SKILL.md · 82 lines

How it starts

The opening of the file, as written. The whole thing — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Technical lineage

Technical lineage maps the physical data flow — including unregistered assets, temporary tables, and source code — across systems. This is broader than business lineage (which only covers cataloged Collibra assets). Almost every lineage question follows the same three-stepit shape:

Resolve the entity with search_lineage_entities (the entry point).
Walk the graph with get_lineage_upstream or get_lineage_downstream.
Selectively resolve the most relevant entities with get_lineage_entity. Do not resolve every ID — summarize from graph structure.

get_lineage_transformation returns SQL or script bodies; only call it when the user asks to see the actual transformation logic. search_lineage_transformations is a specialized search by transformation name, not a general entry point.

Hard rule: lineage IDs are not DGC UUIDs

get_lineage_upstream, get_lineage_downstream, get_lineage_entity, and get_lineage_transformation all use lineage entity IDs, which live in a separate ID space from Collibra DGC asset UUIDs. Passing a DGC UUID directly to any of these tools will fail or return the wrong entity.

The only bridge from a DGC asset to the lineage graph is:

search_lineage_entities(dgcId=<DGC UUID>)  →  lineage entity ID

Always start there when the user gives you a catalog asset.

Column-level lineage limitation

search_lineage_entities cannot reliably resolve columns:

nameContains does not work for columns — the lineage graph does not expose column names through that filter.
dgcId does not reliably resolve column UUIDs because there is no consistent mapping between catalog column UUIDs and lineage column entity IDs.

The workaround: find the parent table first, then walk into its columns from the lineage graph. See references/column-lineage-workaround.md.

Workflows

Upstream sources for an asset

search_lineage_entities(nameContains="<table-name>") or (dgcId=<UUID>) → entity ID
get_lineage_upstream(entityId=<id>) → source entities + transformation IDs (paginated)
Summarize the graph. If the user wants details on a specific source, call get_lineage_entity for that one ID.
Only call get_lineage_transformation if the user wants the SQL or script body.

Read the full file on GitHub · 82 lines

Files

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.

references/column-lineage-workaround.md 1.9 KB

Changes

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.

2mo ago First seen · 82 lines · 26 tokens per session scan A 2038f393acae

Subscribe to this mod's changes

lineage is a skill published in the GitHub repository collibra/chip (37 stars, last pushed yesterday), licensed Apache-2.0. It adds 26 tokens to every session and 860 once invoked, about $0.0001 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.

Analytics and metrics

lineage next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
lineagecollibra/chip	Skill	37	yesterday	Apache-2.0	A	26	Claude Code, Codex
imagegenopenai/codex	Skill	133k	yesterday	Apache-2.0	A	113	Codex
playwright-climicrosoft/playwright	Skill	99k	yesterday	Apache-2.0	A	19	Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	4d ago	MIT	A	200	Claude Code, Codex
systematic-debuggingobra/superpowers	Skill	313k	3d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	95	Claude Code
next-partial-prefetching-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	103	Claude Code