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 semantic-layer-and-metric-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/semantic-layer-and-metric-governance)<a href="https://agentmods.dev/skills/vaquarkhan/data-engineering-agent-skills/semantic-layer-and-metric-governance"><img src="https://agentmods.dev/badge/skills/vaquarkhan/data-engineering-agent-skills/semantic-layer-and-metric-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/semantic-layer-and-metric-governance"><img src="https://agentmods.dev/badge/skills/vaquarkhan/data-engineering-agent-skills/semantic-layer-and-metric-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.00048 | $0.00421 |
| Opus 5 | $0.00024 | $0.00211 |
| Sonnet 5 | $0.00010 | $0.00084 |
| Haiku 4.5 | $0.00005 | $0.00042 |
Grade A, and why
semantic-layer-and-metric-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 9d 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.
What it actually says
Semantic Layer And Metric Governance
Overview
Use this skill when the challenge is consistency of meaning, not just correctness of rows. It helps agents define shared metrics and dimensions so teams stop rebuilding conflicting logic in every downstream tool.
When to Use
- defining or changing business metrics
- introducing a semantic or metric layer
- standardizing dimensions and filters across teams
- governing high-value shared KPIs
Do not rely on ad hoc BI formulas when a metric needs cross-team trust.
Workflow
-
Define the metric contract. Include:
- owner
- exact business meaning
- grain
- numerator and denominator logic
- filters and exclusions
-
Standardize shared dimensions and time logic.
-
Map consumers and expected use cases. A metric used in finance, product, and operations may need stronger governance than a local team report.
-
Keep metric logic centralized where possible.
-
Version or migrate breaking metric changes deliberately.
Common Rationalizations
| Rationalization | Reality |
|---|---|
| "Everyone already knows what revenue means." | Teams often carry different assumptions about refunds, timing, and exclusions. |
| "The BI layer can handle this locally." | Local formulas multiply inconsistency and make audits harder. |
| "Minor metric changes do not need change management." | Even small definition shifts can invalidate trend lines and stakeholder trust. |
Red Flags
- no named metric owner
- filters and exclusions are implicit
- the same KPI exists in multiple incompatible forms
- definition changes are shipped without communication
Verification
- Metric ownership and business meaning are explicit
- Shared dimensions and filters are standardized
- Consumer impact is considered for metric changes
- Breaking definition changes have a migration or communication path
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.
- 9d ago First seen · 61 lines · 48 tokens per session scan A cce42e8ed02c
semantic-layer-and-metric-governance is a skill published in the GitHub repository vaquarkhan/data-engineering-agent-skills (45 stars, last pushed 3mo ago), licensed MIT. It adds 48 tokens to every session and 421 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-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…
kafka-shadowtraffic-java
Generate a TestContainers Java test class that spins up ShadowTraffic in-process to populate a Kafka topic with synthetic data during tests. Invokes the kafka-shadowtraffic skill to build the ShadowTraffic config, then adapts it for a containerized test network and scaffolds a JUnit 5 test class with Kafka, optional…
kafka-connector-review
Review Kafka Connect connector configurations for common misconfigurations using the Lenses MCP server. Checks error handling, DLQ setup, converters, transforms, task count and task health. Use when user says "review connectors", "check connector configs", "why is my connector failing" or asks about Kafka Connect…
kafka-consumer-lag
Analyse Kafka consumer group lag using the Lenses MCP server. Diagnoses lag causes (throughput bottlenecks, rebalancing, partition skew, stalled consumers) and suggests remediation. Use when user says "check consumer lag", "why are consumers slow", "lag report" or asks about consumer group health or offset progress.…
kafka-dlq-review
Review dead letter queue implementations for completeness using the Lenses MCP server. Checks DLQ topic existence, configuration, monitoring, metadata preservation, retry logic, reprocessing paths and connector DLQ alignment. Use when user says "review dead letter queues", "check DLQ setup", "DLQ audit" or asks about…
kafka-perf-review
Review Kafka producer and consumer performance configurations in both the live cluster (via Lenses MCP) and the codebase. Flags un-tuned defaults, anti-patterns and missing best practices. Use when user says "review Kafka performance", "check producer configs", "tune Kafka settings" or asks about throughput, batching…