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/pm-workspaceWrote 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/pm-workspace/banking-detect)<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.
<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>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.00024 | $0.00886 |
| Opus 5 | $0.00012 | $0.00443 |
| Sonnet 5 | $0.00005 | $0.00177 |
| Haiku 4.5 | $0.00002 | $0.00089 |
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.
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.
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
--projectespecificado - Código fuente accesible (local o repo clonado)
- Leer
@.opencode/skills/banking-architecture/references/banking-detection.mdpara 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:
- Domain Entities (35%) — Buscar Account, Transaction, Settlement, KYC...
- Naming & Routes (25%) — APIs /api/payments, topics Kafka, namespaces Banking.*
- Dependencies (15%) — kafka, snowflake, mlflow, swift-sdk, feast...
- Configuration (15%) — KAFKA_BROKER, SNOWFLAKE_, SWIFT_, BIAN_*
- 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)
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.
- 7d ago First seen · 98 lines · 24 tokens per session scan A e1950a23b837
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.
Other commands, from other repositories
valuation-methods
Valuation methods analysis — multiples, DCF inputs, PEG integration, valuation assumption extraction.
merit-reconcile
Preview or check the status of Stripe → Merit payout reconciliation (read-only).
audit-checklist
Perform an internal audit, review controls, or prepare for an external financial audit.
scan
Scan AWS account for cost optimization.
audit
Scan for non-kernel money math. Rebuild critical flows as JournalEntrys. Replay and prove. Complements /ledger-verify.
finops-status
Orientation — say where an opportunity or assignment sits in the five-step FinOps lifecycle and what unlocks next. Useful when a record has no active stage: an opportunity while its assignments do the work, an assignment whose plan has not been approved yet, or a rejected or archived assignment. Read-only; mutates…