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 agentmods add skills/collibra/chip/indexnpx skills add collibra/chip --skill indexgit clone --depth 1 https://github.com/collibra/chipWhat 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 | $0.00017 | $0.00972 |
| Opus 5 | $0.00009 | $0.00486 |
| Sonnet 5 | $0.00003 | $0.00194 |
| Haiku 4.5 | $0.00002 | $0.00097 |
Grade A, and why
index 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 2d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Collibra skills — navigator
This MCP server is a bridge to Collibra Data Governance Center. Skills under
collibra/* document the non-trivial workflows: when tools must be chained, when one ID space
must be bridged to another, and which permissions are required.
When to load which skill
| Task | Skill |
|---|---|
| Find data about a topic by meaning (semantic) vs by exact name (keyword) | collibra/discovery |
| Trace upstream sources, downstream consumers, or impact of a change | collibra/lineage |
| Create any new asset (Business Term, Table, Column, KPI, …) | collibra/asset-create |
| Modify an existing asset's attributes, relations, tags, status, or owners | collibra/asset-edit |
| Register a table (and its dimension tables) as a Collibra Data Product with ports | collibra/data-product-create |
| Generate governed YAML context (semantic blueprints, metric definitions) for an asset | collibra/context |
| Author, validate, run or inspect data quality rules (monitors) on a DQ job | collibra/dq-rules |
| Create DQ rules at scale across many catalog columns (templates or plain-language), with job assignment | collibra/dq-rule-workbench |
If a task is a single tool call with no chaining (e.g. get_asset_details by UUID,
list_asset_types, pull_data_contract_manifest), no skill is needed — the tool's own
description is sufficient.
Where to get each id / publicId
create_asset and edit_asset accept types by UUID, publicId, or display name. When you need
the authoritative UUID or publicId for a type, fetch it from:
| Concept | Tool | Field |
|---|---|---|
| Asset type id / publicId | list_asset_types |
id / publicId |
| Attribute type id / publicId | prepare_create_asset |
attributeSchema[].attributeTypeId / attributeSchema[].publicId |
| Relation type id / publicId | prepare_create_asset |
relationTypes[].relationTypeId / relationTypes[].publicId |
get_asset_details returns attribute and relation display names only (via
assignableAttributes[].name and the relation lists) — use prepare_create_asset to resolve
those names to a type id or publicId.
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.
- 2d ago First seen · 69 lines · 17 tokens per session scan A 4270c57e0611
index is a skill published in the GitHub repository collibra/chip (36 stars, last pushed 4d ago), licensed Apache-2.0. It adds 17 tokens to every session and 972 once invoked, about $0.0001 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…