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 data-sharing-and-publishing-contractsgit 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/data-sharing-and-publishing-contracts)<a href="https://agentmods.dev/skills/vaquarkhan/data-engineering-agent-skills/data-sharing-and-publishing-contracts"><img src="https://agentmods.dev/badge/skills/vaquarkhan/data-engineering-agent-skills/data-sharing-and-publishing-contracts/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/data-sharing-and-publishing-contracts"><img src="https://agentmods.dev/badge/skills/vaquarkhan/data-engineering-agent-skills/data-sharing-and-publishing-contracts.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.00049 | $0.00443 |
| Opus 5 | $0.00024 | $0.00221 |
| Sonnet 5 | $0.00010 | $0.00089 |
| Haiku 4.5 | $0.00005 | $0.00044 |
Grade A, and why
data-sharing-and-publishing-contracts 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 10d 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
Data Sharing And Publishing Contracts
Overview
Use this skill when data leaves the producing team and becomes a product for other teams, systems, or partners. It helps agents define stable publish contracts with ownership, compatibility, and operational expectations.
When to Use
- publishing curated tables or marts
- sharing extracts or files with other teams or partners
- exposing governed data through APIs or reverse ETL
- modifying an existing consumer-facing dataset
Do not publish widely-used data with implicit contracts.
Workflow
-
Define the published contract. Include:
- owner
- audience
- schema
- grain
- delivery method
- freshness and retention expectations
-
Identify compatibility and versioning needs.
-
Define access and usage boundaries. Capture:
- allowed consumers
- privacy constraints
- SLA expectations
- communication path for changes
-
Validate publish readiness before release.
-
Document change policy. Consumers should know what can change, how they will be notified, and how long deprecated behavior lasts.
Common Rationalizations
| Rationalization | Reality |
|---|---|
| "It is just one extract for another team." | One-off exports often become critical dependencies. |
| "Consumers can ask if something changes." | Many consumers only discover changes after failure. |
| "The schema tells them everything they need." | Delivery timing, freshness, retention, and ownership matter too. |
Red Flags
- published outputs have no owner
- delivery or freshness expectations are missing
- breaking changes are shipped without versioning or notice
- access boundaries are unclear for shared datasets
Verification
- The publish contract covers audience, schema, delivery, and freshness
- Ownership and communication path are defined
- Compatibility and access expectations are explicit
- Release readiness is validated before consumers depend on it
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.
- 10d ago First seen · 67 lines · 49 tokens per session scan A 31f70b607c8c
data-sharing-and-publishing-contracts is a skill published in the GitHub repository vaquarkhan/data-engineering-agent-skills (44 stars, last pushed 2mo ago), licensed MIT. It adds 49 tokens to every session and 443 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
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-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-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-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…
kafka-schema-review
Review Kafka schema changes (Avro, Protobuf, JSON Schema) for compatibility and evolution best practices using the Lenses MCP server. Detects breaking changes, missing defaults, schema drift and naming issues. Use when user says "review schema changes", "check schema compatibility", "will this schema break consumers"…