banking-detect

banking-detect is a command for Claude Code from gonzalezpazmonica/pm-workspace. It costs 24 tokens per session (886 once invoked), scanned A, a copy of banking-detect, MIT.

A project-detection command that looks for banking-specific entities, routes, dependencies, configuration, and documentation. It identifies signs such as accounts, transactions, Kafka, Snowflake, SWIFT, or BIAN references.

In plain words
What is it for?
It helps scan a selected or active project, assess its banking signals, and suggest specialised banking tools when those signals are present.
Why use it?
It helps determine whether a codebase is a banking project before applying banking-focused checks. The detailed mode shows which detection areas contributed to the result.

Command for Claude Code

Written for Claude Code: installed under .claude/. Also seen: agent in frontmatter; mentions OpenCode.

Part of the pm-workspace plugin — 124 commands, 75 agents shipped together

Good fit It helps scan a selected or active project, assess its banking signals, and suggest specialised banking tools when those signals are present.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/gonzalezpazmonica/pm-workspace/banking-detect
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.

agentmods badge for banking-detect

README.md
[![agentmods](https://agentmods.dev/badge/commands/gonzalezpazmonica/pm-workspace/banking-detect/github.svg)](https://agentmods.dev/commands/gonzalezpazmonica/pm-workspace/banking-detect)
Your own site
<a href="https://agentmods.dev/commands/gonzalezpazmonica/pm-workspace/banking-detect"><img src="https://agentmods.dev/badge/commands/gonzalezpazmonica/pm-workspace/banking-detect/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.

agentmods 80×15 button for banking-detect

Your own site · 80×15
<a href="https://agentmods.dev/commands/gonzalezpazmonica/pm-workspace/banking-detect"><img src="https://agentmods.dev/badge/commands/gonzalezpazmonica/pm-workspace/banking-detect.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 24 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 886 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 100% copy Near-identical to another mod 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00024 $0.00886
Opus 5 $0.00012 $0.00443
Sonnet 5 $0.00005 $0.00177
Haiku 4.5 $0.00002 $0.00089

Measured 7d ago against content hash e1950a23b837, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

banking-detect 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 7d 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

This is a copy

100% identical to banking-detect — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/commands/banking-detect.md · 98 lines

How it starts

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

/banking-detect [--project {nombre}] [--verbose]

🏦 Savia detecta si tu proyecto es bancario y sugiere herramientas especializadas.


Cargar perfil

Grupo: Verticals — cargar identity.md + projects.md + preferences.md.

Prerequisitos

  • Proyecto activo o --project especificado
  • Código fuente accesible (local o repo clonado)
  • Leer @.opencode/skills/banking-architecture/references/banking-detection.md para el algoritmo

Parámetros

  • --project {nombre} — Proyecto específico (default: proyecto activo)
  • --verbose — Mostrar detalle por fase

Flujo

Paso 1 — Banner y validación

Mostrar: 🏦 Banking Detection · Analizando proyecto... Verificar que el proyecto existe y tiene código fuente.

Paso 2 — Ejecutar 5 fases

Seguir algoritmo de @.opencode/skills/banking-architecture/references/banking-detection.md:

  1. Domain Entities (35%) — Buscar Account, Transaction, Settlement, KYC...
  2. Naming & Routes (25%) — APIs /api/payments, topics Kafka, namespaces Banking.*
  3. Dependencies (15%) — kafka, snowflake, mlflow, swift-sdk, feast...
  4. Configuration (15%) — KAFKA_BROKER, SNOWFLAKE_, SWIFT_, BIAN_*
  5. Documentation (10%) — Menciones de BIAN, TOGAF, ArchiMate, ISO 20022

Paso 3 — Calcular score y clasificar

score = (fase1 × 0.35) + (fase2 × 0.25) + (fase3 × 0.15) + (fase4 × 0.15) + (fase5 × 0.10)
  • ≥55% → 🏦 Proyecto bancario detectado (score: {n}%)
  • 25-54% → 🏦 Posible proyecto bancario (score: {n}%). ¿Confirmas?
  • <25% → ℹ️ No se detectó perfil bancario. ¿Es un proyecto de banca?

Paso 4 — Sugerir herramientas

Si banking confirmado, mostrar:

🏦 Herramientas bancarias disponibles:
  /banking-bian            — Validar arquitectura BIAN
  /banking-eda-validate    — Validar pipelines Kafka/EDA
  /banking-data-governance — Auditar gobierno de datos
  /banking-mlops-audit     — Auditar pipeline ML/IA
  /vertical-finance        — Compliance regulatorio (SOX, Basel, PCI DSS)

Read the full file on GitHub · 98 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.

  1. 7d ago First seen · 98 lines · 24 tokens per session scan A e1950a23b837

Subscribe to this mod's changes

banking-detect is a command published in the GitHub repository gonzalezpazmonica/pm-workspace (49 stars, last pushed 4d ago), licensed MIT. It adds 24 tokens to every session and 886 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to banking-detect, differing in 0 lines, and is treated as a copy.