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 johnqtcg/awesome-skills --skill kafka-event-driven-designgit clone --depth 1 https://github.com/johnqtcg/awesome-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/johnqtcg/awesome-skills/kafka-event-driven-design)<a href="https://agentmods.dev/skills/johnqtcg/awesome-skills/kafka-event-driven-design"><img src="https://agentmods.dev/badge/skills/johnqtcg/awesome-skills/kafka-event-driven-design/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/johnqtcg/awesome-skills/kafka-event-driven-design"><img src="https://agentmods.dev/badge/skills/johnqtcg/awesome-skills/kafka-event-driven-design.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 234 Skill allows unbounded resource consumption (API calls, storage, compute). Without rate limits or quotas, a compromised or misbehaving agent can cause denial-of-service or cost overruns.Fix: Set explicit rate limits, timeouts, and resource quotas for API calls, file operations, and compute. Implement circuit breakers for runaway loops.
- medium Excessive Agency · line 314 Skill allows unbounded resource consumption (API calls, storage, compute). Without rate limits or quotas, a compromised or misbehaving agent can cause denial-of-service or cost overruns.Fix: Set explicit rate limits, timeouts, and resource quotas for API calls, file operations, and compute. Implement circuit breakers for runaway loops.
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.00191 | $0.07675 |
| Opus 5 | $0.00096 | $0.03837 |
| Sonnet 5 | $0.00038 | $0.01535 |
| Haiku 4.5 | $0.00019 | $0.00768 |
Grade A, and why
kafka-event-driven-design 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 — 425 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kafka Event-Driven Design Review
Quick Reference
§1 Scope · §2 Mandatory Gates · §3 Depth & Reference Loading · §4 Degradation Modes · §5 Design Checklist · §6 Partition Design · §7 Anti-Examples · §8 Scorecard · §9 Output Contract
Before scoring a version-sensitive configuration item, read
references/version-client-matrix.md. Kafka defaults changed materially at 3.0
and again at 4.0, and the four major client libraries disagree with each other.
Which items are version-sensitive — and which fact each one needs — is §2's
Minimum context per scored item; most of the checklist needs no version at all.
§1 Scope
In scope — Kafka event-driven architecture for production backend services:
- Topic design (naming, partition count, replication factor, retention)
- Partition key strategy (ordering guarantees, hot partition avoidance)
- Event schema design (Avro/Protobuf/JSON Schema, schema evolution, compatibility)
- Producer configuration (acks, retries, idempotence, transactional producers)
- Consumer group design (assignment strategy, rebalance handling, commit strategy)
- Idempotent consumption (deduplication, idempotency keys, exactly-once semantics)
- Dead letter queue (DLQ) and retry patterns
- Backpressure and consumer lag management
- Schema Registry integration and compatibility modes
Out of scope — say so and redirect rather than answering partially:
| Out of scope | Why it is not this skill |
|---|---|
| Broker sizing, heap/page-cache tuning, disk layout | Cluster operations, not client design |
| KRaft/ZooKeeper administration, controller config, 3.9→4.x migration | Platform runbook territory |
| Partition reassignment tooling, cruise-control balancing, quotas | Operational, though its client-visible consequences (AE-12 key remapping) are in scope |
| ACL administration and principal management | In scope only as a design requirement (§5.5 item 16), not as operator commands |
| MirrorMaker / cross-cluster replication topology | Separate architecture |
| Kafka Streams / Kafka Connect internals | Different programming models with their own semantics |
Application code unrelated to Kafka → go-code-reviewer |
|
General REST/gRPC API design → api-design |
What ships with it
35 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/consumer-anti-examples.md 14 KB
- references/consumer-failure-modes.md 18 KB
- references/event-schema-patterns.md 22 KB
- references/version-client-matrix.md 12 KB
- scripts/gen_coverage.py 12 KB runs code
- scripts/lint_kafka_docs.py 54 KB runs code
- scripts/model_eval.py 30 KB runs code
- scripts/mutation_sweep.py 16 KB runs code
- scripts/paraphrase_corpus.py 16 KB runs code
- scripts/run_regression.sh 2.0 KB runs code
- scripts/tests/COVERAGE.md 9.1 KB
- scripts/tests/golden/001_acks_not_all.json 1.4 KB
- scripts/tests/golden/002_no_idempotent_consumer.json 1.4 KB
- scripts/tests/golden/003_no_dlq.json 1.8 KB
- scripts/tests/golden/004_null_partition_key.json 1.4 KB
- scripts/tests/golden/005_no_schema_metadata.json 1.6 KB
- scripts/tests/golden/006_no_schema_compatibility.json 1.6 KB
- scripts/tests/golden/007_well_formed_design.json 1.6 KB
- scripts/tests/golden/008_good_outbox_pattern.json 1.2 KB
- scripts/tests/golden/009_degraded_no_context.json 1.6 KB
- scripts/tests/golden/010_greenfield_design.json 1.7 KB
- scripts/tests/golden/011_no_lag_monitoring.json 1.3 KB
- scripts/tests/golden/012_eos_removed_api.json 2.0 KB
- scripts/tests/golden/013_dlq_publish_unchecked.json 1.9 KB
- scripts/tests/golden/014_kafka4_assignor_conflict.json 1.9 KB
- scripts/tests/golden/015_outbox_as_kafka_txn.json 1.9 KB
- scripts/tests/golden/016_cache_ttl_dedup.json 2.0 KB
- scripts/tests/golden/017_modern_java_defaults.json 1.8 KB
- scripts/tests/golden/018_pii_compacted_topic.json 1.9 KB
- scripts/tests/golden/019_event_sourcing_compaction.json 2.1 KB
- scripts/tests/golden/020_copied_lag_threshold.json 1.9 KB
- scripts/tests/golden/021_static_membership_overclaim.json 2.2 KB
- scripts/tests/test_golden_scenarios.py 16 KB runs code
- scripts/tests/test_skill_contract.py 44 KB runs code
- scripts/trigger_eval.py 16 KB runs code
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 · 425 lines · 191 tokens per session scan A 8a1af37ecaad
kafka-event-driven-design is a skill published in the GitHub repository johnqtcg/awesome-skills (30 stars, last pushed yesterday), licensed MIT. It adds 191 tokens to every session and 7,675 once invoked, about $0.0010 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
security-compliance
Guides security professionals in implementing defense-in-depth security architectures, achieving compliance with industry frameworks (SOC2, ISO27001, GDPR, HIPAA), conducting threat modeling and risk assessments, managing security operations and incident response, and embedding security throughout the SDLC.
stride-analysis-patterns
Apply STRIDE methodology to systematically identify threats. Use when analyzing system security, conducting threat modeling sessions, or creating security documentation.
cache-components
Expert guidance for Next.js Cache Components and Partial Prerendering (PPR). PROACTIVE ACTIVATION: Use this skill automatically when working in Next.js projects that have cacheComponents: true in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best…
manage-skills
A maintenance workflow for checking whether project verification skills still cover the code and rules that changed during a session.
blind-spot-pass
Use before starting work in a domain you don't know well, to surface the "unknown unknowns" — the things you don't even know to ask about — and learn just enough to prompt and decide well. Implements the "blind spot pass" pattern from Anthropic's Fable "finding your unknowns" field guide. Triggers when you say "I'm…
skill-factory
A workflow that examines completed session work and turns reusable patterns into Claude Code skills.