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 vaquarkhan/data-engineering-agent-skills --skill microsoft-purview-and-azure-data-governancegit clone --depth 1 https://github.com/vaquarkhan/data-engineering-agent-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/vaquarkhan/data-engineering-agent-skills/microsoft-purview-and-azure-data-governance)<a href="https://agentmods.dev/skills/vaquarkhan/data-engineering-agent-skills/microsoft-purview-and-azure-data-governance"><img src="https://agentmods.dev/badge/skills/vaquarkhan/data-engineering-agent-skills/microsoft-purview-and-azure-data-governance/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/vaquarkhan/data-engineering-agent-skills/microsoft-purview-and-azure-data-governance"><img src="https://agentmods.dev/badge/skills/vaquarkhan/data-engineering-agent-skills/microsoft-purview-and-azure-data-governance.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00066 | $0.00627 |
| Opus 5 | $0.00033 | $0.00313 |
| Sonnet 5 | $0.00013 | $0.00125 |
| Haiku 4.5 | $0.00007 | $0.00063 |
Grade A, and why
microsoft-purview-and-azure-data-governance 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Microsoft Purview And Azure Data Governance
Overview
Use this skill when Microsoft Purview is the governance control plane for Azure data platforms. It helps agents design metadata collections, classification strategy, scan scope, lineage expectations, and governed publish behavior across Microsoft analytics surfaces.
When to Use
- designing
Purviewcollection and ownership structure - defining scans, classifications, glossary, and lineage expectations
- governing datasets across
ADLS,Synapse,Data Factory,Azure Databricks, orFabric - improving trusted discovery and certification for shared data products
- aligning Azure-native governance with privacy, security, and release controls
Do not assume Purview is only a catalog tool. It often becomes the platform evidence and policy surface for governed analytics.
Workflow
-
Define governance scope. Clarify:
- in-scope platforms
- business domains
- critical data products
- stewardship and ownership model
-
Design the metadata operating model. Decide:
- collections
- glossary boundaries
- classifications and sensitivity labels
- scan cadence and ownership
-
Define trusted publish behavior. Require:
- certification or endorsement rules
- lineage completeness expectations
- ownership visibility
- ties to regulated-data controls where relevant
-
Align Azure services with governance. Check how
Purviewworks withADLS,Synapse,Data Factory,Databricks, andFabricrather than treating each system separately. -
Validate operational sustainability. Make sure scans, classifications, and lineage remain useful as assets, teams, and environments grow.
Common Rationalizations
| Rationalization | Reality |
|---|---|
| "Scanning everything is the same as governing it." | Governance also needs ownership, trust signals, and useful boundaries for consumers. |
| "Purview can be added after pipelines are done." | Late governance usually means weak lineage, poor certification, and inconsistent discovery. |
| "Each Azure service team can manage metadata separately." | Fragmented governance weakens platform-wide trust and policy evidence. |
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 · 74 lines · 66 tokens per session scan A 090deccba1a4
microsoft-purview-and-azure-data-governance is a skill published in the GitHub repository vaquarkhan/data-engineering-agent-skills (45 stars, last pushed 3mo ago), licensed MIT. It adds 66 tokens to every session and 627 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
kafka-shadowtraffic
Generate a ShadowTraffic configuration to populate a Kafka topic with realistic synthetic data. Discovers the target topic, its key and value schemas, and the correct serializers from the live cluster via any attached Kafka MCP server, then writes a ready-to-run shadowtraffic-config.json and Docker command. Use when…
responsible-ai
Responsible AI governance skill for software development. Enforces a 7-pillar RAI framework (tenant/data isolation, PII protection, citation integrity, confidence scoring, hallucination prevention, bias mitigation, content provenance) during development. Use when building or reviewing code touching LLM pipelines…
9router
Entry point for 9Router — local/remote AI gateway with OpenAI-compatible REST for chat, image, TTS, embeddings, web search, web fetch. Use when the user mentions 9Router, NINEROUTERURL, or wants AI without writing provider boilerplate. This skill covers setup + indexes capability skills; fetch the relevant capability…
markitdown
Convert files and office documents to Markdown. Supports PDF, DOCX, PPTX, XLSX, images (with OCR), audio (with transcription), HTML, CSV, JSON, XML, ZIP, YouTube URLs, EPubs and more.
best-practices
Transforms vague prompts into optimized Claude Code prompts. Adds verification, specific context, constraints, and proper phasing. Invoke with /best-practices.
annotating-task-lineage
Annotate Airflow tasks with data lineage using inlets and outlets. Use when the user wants to add lineage metadata to tasks, specify input/output datasets, or enable lineage tracking for operators without built-in OpenLineage extraction.