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/asset-createnpx skills add collibra/chip --skill asset-creategit 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.00020 | $0.01059 |
| Opus 5 | $0.00010 | $0.00530 |
| Sonnet 5 | $0.00004 | $0.00212 |
| Haiku 4.5 | $0.00002 | $0.00106 |
Grade A, and why
asset-create 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Creating assets
create_asset is a single-call write tool that resolves human-friendly identifiers
server-side: assetType accepts UUID, publicId (e.g. "BusinessTerm"), or display name
(e.g. "Business Term"); domain accepts UUID or name; status accepts UUID or status
name; attributes reference attribute types by name or typeId. You almost never need to
pre-resolve any of these.
Hard rules
create_assetis self-sufficient. Do not callprepare_create_assetfirst by default.create_assetdoes its own resolution, validation, and duplicate check, and its error responses include suggestions for self-correction.- Write Markdown in RICH_TEXT attributes. Chip converts Markdown to HTML server-side for
any RICH_TEXT attribute (e.g.
Definition). Use**bold**,[links](url), lists, and headings naturally. Never pass HTML; never pre-render Markdown yourself. Seeshared/rich-text-markdown.mdfor the full rules. - Read the
statusfield in the response. Branch onsuccess,duplicate_found,validation_error, orerror— do not assume success.
Workflow
- Call
create_assetwithname,assetType(UUID, publicId, or display name),domain(UUID or name), optionalstatus, and optionalattributes. - Branch on the response
status:success— done. The response includes the new asset's UUID and a per-attribute outcome list. Report the UUID to the user.duplicate_found— an asset with the samenamealready exists in the resolved (assetType, domain). The response includes the existing asset's ID. Confirm with the user before retrying withallowDuplicate: true. Do not auto-retry — duplicates are usually a mistake.validation_error— the error message includes suggestions (available asset types, compatible domains, valid attribute names). Self-correct from the suggestions and retry. Only escalate to the user if a second attempt also fails.error— an unexpected downstream Collibra failure. Surface the message to the user; do not retry blindly.
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 · 88 lines · 20 tokens per session scan A a1ce295cef56
asset-create is a skill published in the GitHub repository collibra/chip (36 stars, last pushed 5d ago), licensed Apache-2.0. It adds 20 tokens to every session and 1,059 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…