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.
git clone --depth 1 https://github.com/gonzalezpazmonica/saviaWrote 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/commands/gonzalezpazmonica/savia/banking-eda-validate)<a href="https://agentmods.dev/commands/gonzalezpazmonica/savia/banking-eda-validate"><img src="https://agentmods.dev/badge/commands/gonzalezpazmonica/savia/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.
<a href="https://agentmods.dev/commands/gonzalezpazmonica/savia/banking-eda-validate"><img src="https://agentmods.dev/badge/commands/gonzalezpazmonica/savia/banking-eda-validate.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.00027 | $0.00899 |
| Opus 5 | $0.00014 | $0.00449 |
| Sonnet 5 | $0.00005 | $0.00180 |
| Haiku 4.5 | $0.00003 | $0.00090 |
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 5d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- banking-eda-validate — 100% identical, 0 lines differ
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 |
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.
- 5d ago First seen · 107 lines · 27 tokens per session scan A ca6e72d1eabb
banking-eda-validate is a command published in the GitHub repository gonzalezpazmonica/savia (50 stars, last pushed yesterday), licensed MIT. It adds 27 tokens to every session and 899 once invoked, about $0.0001 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-09-06.
Other commands, from other repositories
vios-architecture
Explain the VIOS stream-processor and sensor microservice deployment architecture: containers, ingress, RTSP, file-upload, WebRTC, Envoy, SDR, routing, and event flow.
fastapi
FastAPI application design and implementation conventions. Use this skill when building, updating, or reviewing FastAPI services, routers, dependencies, request/response schemas, streaming endpoints, or API tests. Trigger on FastAPI-specific work such as path operation design, dependency injection, response models…
graphql
Build version-safe Shopify Admin GraphQL queries and mutations, optimize query cost, and implement error handling.
add-webhook
Add webhook subscriptions for Shopify events (orders, products, inventory) with signature verification and handler routing.
migrate-azure-to-railway
Migrate this Azure-hosted project to Railway. Convert Azure Functions to Express.js API routes. Migrate Azure Table Storage to PostgreSQL with Prisma ORM. Update environment variables for Railway platform. Create railway.toml configuration and Dockerfile for deployment. Set up staging and production environments.…
checklist
Generate a custom checklist for the current feature based on user requirements.