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-contract-testing-with-schema-registrygit 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-contract-testing-with-schema-registry)<a href="https://agentmods.dev/skills/vaquarkhan/data-engineering-agent-skills/data-contract-testing-with-schema-registry"><img src="https://agentmods.dev/badge/skills/vaquarkhan/data-engineering-agent-skills/data-contract-testing-with-schema-registry/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-contract-testing-with-schema-registry"><img src="https://agentmods.dev/badge/skills/vaquarkhan/data-engineering-agent-skills/data-contract-testing-with-schema-registry.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.00044 | $0.01012 |
| Opus 5 | $0.00022 | $0.00506 |
| Sonnet 5 | $0.00009 | $0.00202 |
| Haiku 4.5 | $0.00004 | $0.00101 |
Grade A, and why
data-contract-testing-with-schema-registry 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.
How it starts
The opening of the file, as written. The whole thing — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Data Contract Testing With Schema Registry
Overview
Use this skill when contracts must be tested through registry-backed compatibility rules, not only by convention. It helps agents make event contract validation a blocking part of build and release behavior with automated testing, consumer impact analysis, and evidence-driven release gates.
When to Use
- testing event contract changes before production release
- validating schema compatibility as part of CI/CD pipelines
- coordinating producer and consumer schema evolution across teams
- enforcing registry-backed contract quality gates before deployment
- building release evidence that proves schema safety
Do not use this when schemas are not managed through a registry or when the system has no shared event contracts.
Workflow
-
Define the contract and compatibility target per subject. Include:
- which schema registry subjects are in scope
- the compatibility level required:
BACKWARD,FORWARD,FULL, orTRANSITIVEvariants - who owns the contract (producing team, platform team, or shared)
- which consumers depend on each subject and their minimum supported version
-
Implement contract tests in CI.
- register the proposed schema against the registry's compatibility endpoint
- use the registry's
/compatibilityAPI to check before merging - fail the build if compatibility is violated
- produce test output showing which rules passed or failed
- run tests against both the latest registered version and specific consumer versions
-
Test representative producer and consumer scenarios.
- serialize sample records with the new schema and deserialize with the old
- verify that default values produce correct behavior for removed or added fields
- test edge cases: null handling, enum additions, nested record changes
- for Protobuf: test field number stability and reserved field behavior
- for Avro: test union type evolution and logical type compatibility
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 · 95 lines · 44 tokens per session scan A 6524c29fa413
data-contract-testing-with-schema-registry is a skill published in the GitHub repository vaquarkhan/data-engineering-agent-skills (44 stars, last pushed 2mo ago), licensed MIT. It adds 44 tokens to every session and 1,012 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-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…
workflow-patterns
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.
skillshare-implement-feature
Implement a feature from a spec file or description using TDD workflow. Use this skill whenever the user asks to: add a new CLI command, implement a feature from a spec, build new functionality, add a flag, create a new internal package, or write Go code for skillshare. This skill enforces test-first development…
designing-tests
Designs and implements testing strategies for any codebase. Use when adding tests, improving coverage, setting up testing infrastructure, debugging test failures, or when asked about unit tests, integration tests, or E2E testing.
Changelog Test Mapper
Map changelog entries and release notes to affected test cases, ensuring every user-facing change has corresponding test coverage verification.
Error Boundary Tester
Validate error boundary implementations in React and other frameworks ensuring graceful degradation, proper fallback UI rendering, and error recovery flows.