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-bian)<a href="https://agentmods.dev/commands/gonzalezpazmonica/pm-workspace/banking-bian"><img src="https://agentmods.dev/badge/commands/gonzalezpazmonica/pm-workspace/banking-bian/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-bian"><img src="https://agentmods.dev/badge/commands/gonzalezpazmonica/pm-workspace/banking-bian.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.00019 | $0.00898 |
| Opus 5.5 | $0.00008 | $0.00359 |
| Sonnet 5.5 | $0.00004 | $0.00180 |
| Haiku 4.5 | $0.00002 | $0.00090 |
Grade A, and why
banking-bian 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 1mo 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-bian — 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/banking-bian [--project {nombre}] [--diagram] [--level 1-5]
🏦 Valida tu arquitectura contra el framework BIAN y genera vistas ArchiMate.
Cargar perfil y skill
Grupo: Architecture & Tech — cargar identity.md + projects.md + preferences.md.
Skill: @.opencode/skills/banking-architecture/SKILL.md
Reference: @.opencode/skills/banking-architecture/references/bian-framework.md
Parámetros
--project {nombre}— Proyecto (default: activo)--diagram— Generar diagramas ArchiMate en Mermaid--level {1-5}— Profundidad de validación (1=naming, 5=governance)
Flujo
Paso 1 — Detectar microservicios
Escanear proyecto: Docker Compose, Kubernetes manifests, service directories. Listar servicios encontrados con sus APIs expuestas.
Paso 2 — Mapear a BIAN Service Domains
Para cada microservicio detectado, intentar mapeo a BIAN:
payment-service → Payment Initiation / Payment Execution
account-service → Current Account / Savings Account
settlement-engine → Settlement
scoring-service → Credit Administration (Credit Scoring)
fraud-detector → Fraud Detection
kyc-service → Party Authentication
notification-service → Customer Event History
Identificar servicios NO mapeables (posible gap o god service).
Paso 3 — Validar adherencia por nivel
Nivel 1 — Naming: ¿Servicios siguen nomenclatura BIAN? Nivel 2 — Boundaries: ¿Cada servicio respeta los límites del domain? Nivel 3 — APIs: ¿Service operations siguen el patrón BIAN? Nivel 4 — Data: ¿Business Objects siguen metamodelo BIAN? Nivel 5 — Governance: ¿Architecture Board valida cambios?
Paso 4 — Detectar anti-patterns
Buscar en el reference:
- God Service — Un servicio cubre múltiples BIAN domains
- Fragmented Domain — Un domain partido en demasiados servicios
- Missing Gateway — Acceso directo a BD sin API
- Coupled Settlement — Settlement acoplado a payments
- Shadow IT — Servicios no registrados
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.
- 1mo ago First seen · 108 lines · 19 tokens per session scan A 0da644131c8e
banking-bian is a command published in the GitHub repository gonzalezpazmonica/pm-workspace (50 stars, last pushed 5d ago), licensed MIT. It adds 19 tokens to every session and 898 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to banking-bian, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
banking-bian
Validar arquitectura contra estándar BIAN y generar diagramas ArchiMate.
profile
Save, load, inspect, update, reset, or delete diagram-design client profiles.
init
Initialize configurations for Supabase local development.
design-audit
Audit the rendered design of live sites. Evidence capture first, then one critique per site. Argument is a URL, a repo name, or all.
build
Discover an AI Gateway's models and MCP tools, retrieve a credential, and integrate them into your app — call a model, connect MCP tools, or scaffold a runnable agent.
4-generate
Run Stage 4 of the design system skill generation pipeline: parallel skill file generation.