What is banking-eda-validate?

An architecture-checking command for event-driven banking systems built around Kafka and related messaging tools. Event-driven architecture lets services communicate by publishing and receiving events, while a dead-letter queue stores messages that could not be processed.

It helps inspect Kafka infrastructure, topic naming and partitioning, schema registries, event stores, outbox tables, and reliability settings.

It helps find design and reliability problems in topics, message schemas, retries, and distributed workflows before they cause failures. It also checks patterns such as Sagas and idempotency, which help coordinate multi-step work and prevent duplicate processing.

banking-eda-validate — Command for Claude Code by gonzalezpazmonica

Install

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.

Clone the repo

git clone --depth 1 https://github.com/gonzalezpazmonica/pm-workspace

Made for: Claude Code.

Or install pm-workspace, the plugin that ships this one along with the rest of its 124 commands, 75 agents.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/gonzalezpazmonica/pm-workspace/banking-eda-validate/github.svg)](https://agentmods.dev/commands/gonzalezpazmonica/pm-workspace/banking-eda-validate)

Your own site

<a href="https://agentmods.dev/commands/gonzalezpazmonica/pm-workspace/banking-eda-validate"><img src="https://agentmods.dev/badge/commands/gonzalezpazmonica/pm-workspace/banking-eda-validate/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/gonzalezpazmonica/pm-workspace/banking-eda-validate"><img src="https://agentmods.dev/badge/commands/gonzalezpazmonica/pm-workspace/banking-eda-validate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 27 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 899 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00027	$0.00899
Opus 5.5	$0.00011	$0.00360
Sonnet 5.5	$0.00005	$0.00180
Haiku 4.5	$0.00003	$0.00090

Measured 2mo ago against content hash ca6e72d1eabb, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

banking-eda-validate 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 2mo 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

banking-eda-validate — 100% identical, 0 lines differ

.claude/commands/banking-eda-validate.md · 107 lines

How it starts

The opening of the file, as written. The whole thing — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/banking-eda-validate [--project {nombre}] [--fix] [--focus topics|schemas|reliability]

🏦 Valida tu arquitectura event-driven: Kafka, schemas, Sagas, reliability patterns.

Cargar perfil y skill

Grupo: Architecture & Tech — cargar identity.md + projects.md + preferences.md. Reference: @.opencode/skills/banking-architecture/references/eda-patterns-banking.md

Parámetros

--project {nombre} — Proyecto (default: activo)
--fix — Generar correcciones sugeridas (default: solo análisis)
--focus {area} — Focalizar en: topics | schemas | reliability (default: all)

Flujo

Paso 1 — Detectar infraestructura EDA

Buscar en código, config y Docker/K8s:

Kafka brokers, topics, consumer groups
Schema Registry (Confluent, Apicurio, AWS Glue)
Event stores, outbox tables
Message brokers alternativos (AMQ, MSK, Pulsar)

Paso 2 — Validar Topic Design

Verificar convenciones de naming, partitioning y configuración:

Check	Esperado	Criticidad
Naming convention	`{domain}.{entity}.{event}`	WARNING
Partitioning key	account_id o correlation_id	CRITICAL
Retention policy	≥7 días para banca	WARNING
Replication factor	≥3 en producción	CRITICAL
DLQ configurado	Sí para cada consumer	CRITICAL
Compaction	Solo para snapshots/state	INFO

Paso 3 — Validar Schemas

Si hay Schema Registry:

Compatibilidad: BACKWARD o FULL recomendado
Formato: Avro o Protobuf (JSON sin schema = ❌)
Evolución: verificar que no hay breaking changes
Campos obligatorios: event_id, timestamp, correlation_id, source

Paso 4 — Validar Reliability Patterns

Pattern	Check	Criticidad
Idempotencia	Consumer dedup por event_id	CRITICAL
Outbox Pattern	Evento en tabla + Kafka en misma TX	CRITICAL
Circuit Breaker	Configurado para servicios downstream	WARNING
Retry con backoff	Exponential backoff, max retries	WARNING
Dead Letter Queue	DLQ con alertas	CRITICAL
Exactly-once	Kafka Transactions habilitadas	WARNING

Read the full file on GitHub · 107 lines

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.

2mo ago First seen · 107 lines · 27 tokens per session scan A ca6e72d1eabb

Subscribe to this mod's changes

banking-eda-validate is a command published in the GitHub repository gonzalezpazmonica/pm-workspace (51 stars, last pushed 5d ago), licensed MIT. It adds 27 tokens to every session and 899 once invoked, about $0.0001 per session on Opus 5.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.

Backend and APIs Containers DevOps and cloud

banking-eda-validate next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
banking-eda-validategonzalezpazmonica/pm-workspace	Command	51	5d ago	MIT	A	27	Claude Code
vios-architectureNVIDIA-AI-Blueprints/video-search-and-summarization	Command	2.0k	yesterday	Apache-2.0	A	42	Claude Code
deploymentJustdvp/claude-code-templates	Command	7	25d ago	MIT	A	0	Claude Code
setup-projectMadAppGang/claude-code	Command	287	7mo ago	MIT	A	29	Claude Code
banking-eda-validategonzalezpazmonica/savia	Command	49	yesterday	MIT	A	27	Claude Code
migrate-azure-to-railwayAshikparvez89/larouex-fullstack-plugin	Command	3	24d ago	MIT	A	0	Claude Code
http-serviceMadAppGang/magus	Command	14	yesterday	MIT	A	27	Claude Code