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 datahub-project/datahub-skills --skill using-datahubgit clone --depth 1 https://github.com/datahub-project/datahub-skillsWrote 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/datahub-project/datahub-skills/using-datahub)<a href="https://agentmods.dev/skills/datahub-project/datahub-skills/using-datahub"><img src="https://agentmods.dev/badge/skills/datahub-project/datahub-skills/using-datahub.svg" alt="Measured on agentmods" 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.00044 | $0.00925 |
| Opus 5 | $0.00022 | $0.00463 |
| Sonnet 5 | $0.00009 | $0.00185 |
| Haiku 4.5 | $0.00004 | $0.00093 |
Grade A, and why
using-datahub 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 8d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Using DataHub Skills
You have access to 5 DataHub catalog interaction skills. Use this guide to route the user's request to the correct skill.
Skill Routing Table
| User Intent | Skill | Command |
|---|---|---|
| Find or discover entities (search, browse, filter, list) | Search | /datahub-search |
| Answer a question about the catalog ("who owns X?", "how many X?") | Search | /datahub-search |
| Update metadata (descriptions, tags, glossary terms, ownership, deprecation) | Enrich | /datahub-enrich |
| Explore lineage (upstream, downstream, impact, root cause, dependencies) | Lineage | /datahub-lineage |
| Data quality (assertions, incidents, health checks) | Quality | /datahub-quality |
| Notifications (subscribe to assertion failures, incidents) | Quality | /datahub-quality |
| Install CLI, authenticate, verify connection | Setup | /datahub-setup |
| Configure default scopes and profiles | Setup | /datahub-setup |
Disambiguation Rules
When the intent is ambiguous, use these rules:
"Tag" requests
- All tag operations (PII, sensitive, important, reviewed, team-x) → Enrich (general metadata)
"Domain" requests
- Filter search to a domain → Search (scoped search)
- Configure default domain → Setup (profile configuration)
"Quality" or "health" requests
- Failing assertions, active incidents, health status → Quality
- Create assertions, run quality checks, raise incidents → Quality
- Subscribe to assertion failures or incidents → Quality
- Metadata quality/documentation/ownership coverage → Use Search to gather the data and synthesize the answer
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.
- 8d ago First seen · 85 lines · 44 tokens per session scan A a10adcd2e631
using-datahub is a skill published in the GitHub repository datahub-project/datahub-skills (38 stars, last pushed 10d ago), licensed Apache-2.0. It adds 44 tokens to every session and 925 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-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…