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 avro-protobuf-json-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/avro-protobuf-json-schema-registry)<a href="https://agentmods.dev/skills/vaquarkhan/data-engineering-agent-skills/avro-protobuf-json-schema-registry"><img src="https://agentmods.dev/badge/skills/vaquarkhan/data-engineering-agent-skills/avro-protobuf-json-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/avro-protobuf-json-schema-registry"><img src="https://agentmods.dev/badge/skills/vaquarkhan/data-engineering-agent-skills/avro-protobuf-json-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.00051 | $0.01066 |
| Opus 5 | $0.00026 | $0.00533 |
| Sonnet 5 | $0.00010 | $0.00213 |
| Haiku 4.5 | $0.00005 | $0.00107 |
Grade A, and why
avro-protobuf-json-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 12d 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.
Avro Protobuf JSON Schema Registry
Overview
Use this skill when schema management for events must be explicit and enforceable. It helps agents coordinate producer changes, consumer compatibility, registry policy, and versioned contracts across teams sharing event streams.
When to Use
- adopting a schema registry for event-driven systems
- defining or modifying Avro, Protobuf, or JSON Schema definitions
- setting compatibility policies for topics or subjects
- coordinating producer schema changes across multiple consumers
- enforcing contract governance for multi-team event ecosystems
Do not use this when schemas are managed purely through application code with no shared registry or when the system has a single producer-consumer pair with no evolution concerns.
Workflow
-
Define schema ownership and subject naming. Include:
- who owns each schema subject (team, service, domain)
- subject naming strategy:
TopicNameStrategy,RecordNameStrategy, orTopicRecordNameStrategy - where schemas are stored: Confluent Schema Registry, AWS Glue Schema Registry, Apicurio, or equivalent
- schema source of truth: registry-first or code-first with CI sync
-
Choose the schema format intentionally.
Avro: strong ecosystem support, compact binary, requires registry for deserializationProtobuf: excellent for multi-language teams, supports nested messages and servicesJSON Schema: human-readable, looser typing, easier adoption but weaker guarantees- consider: serialization size, language support, tooling maturity, and team familiarity
- do not mix formats within a single domain unless isolation is absolute
-
Define and enforce compatibility policies.
BACKWARD: new schema can read old data (safe for consumer-first evolution)FORWARD: old schema can read new data (safe for producer-first evolution)FULL: both backward and forward compatible (safest, most restrictive)NONE: no compatibility checking (use only for development or isolated topics)- set policy per subject, not globally — different topics have different evolution needs
- test compatibility in CI before publishing schema changes
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.
- 12d ago First seen · 95 lines · 51 tokens per session scan A c4cb31d988a1
avro-protobuf-json-schema-registry is a skill published in the GitHub repository vaquarkhan/data-engineering-agent-skills (45 stars, last pushed 3mo ago), licensed MIT. It adds 51 tokens to every session and 1,066 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-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-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-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-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"…