What is bce-diagrams?

A skill for creating high-level diagrams of how business components, subsystems, services, and external systems interact. A business component is a group of code organized around one responsibility, such as orders or payments.

Making architecture overviews, component and subsystem diagrams, service interaction maps, system landscapes, and integration maps.

It turns a complex system’s relationships into an overview that is easier to inspect than package structures or source code.

bce-diagrams — Skill for Claude Code by AdamBien

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.

Any agent

npx skills add AdamBien/airails --skill bce-diagrams

Clone the repo

git clone --depth 1 https://github.com/AdamBien/airails

Made for: Claude Code.

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/skills/adambien/airails/bce-diagrams/github.svg)](https://agentmods.dev/skills/adambien/airails/bce-diagrams)

Your own site

<a href="https://agentmods.dev/skills/adambien/airails/bce-diagrams"><img src="https://agentmods.dev/badge/skills/adambien/airails/bce-diagrams/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/skills/adambien/airails/bce-diagrams"><img src="https://agentmods.dev/badge/skills/adambien/airails/bce-diagrams.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 122 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 834 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. Third-party audits

NVIDIA SkillSpector warn 7 Sept 2026

SkillSpector: 1 finding, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

medium Excessive Agency · line 24
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.

Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.

How audits are shown

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.00122	$0.00834
Opus 5	$0.00061	$0.00417
Sonnet 5	$0.00024	$0.00167
Haiku 4.5	$0.00012	$0.00083

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

Security

Grade A, and why

bce-diagrams 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 11d 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.

documentation/bce-diagrams/SKILL.md · 50 lines

How it starts

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

BCE Overview Diagrams

Create diagrams that show interactions and dependencies between business components (BCs), subsystems, and external services at a high level of abstraction. Based on BCE architecture (see bce.design).

BCE Terminology

Business Component (BC) — a feature-based unit grouping related boundary, control, and entity packages. Named after its domain responsibility (e.g., orders, payments, speakers).
Boundary — the BC's external interface: JAX-RS resources, facades, health checks.
Subsystem — a grouping of related BCs at a higher level of abstraction.
In "between components" mode, show BCs and subsystems as opaque nodes. In "within components" mode, expand BCs to show their boundary, control, and entity layers.

Workflow

Gather information - Identify BCs, subsystems, and external services to visualize. Analyze the codebase package structure ([org].[project].[bc].[boundary|control|entity]) or use the user's description.
Choose detail level and format - Ask the user using a single AskUserQuestion call with two questions:
- Detail level: "Between components" (each BC is a single opaque node) or "Within components" (show boundary, control, entity layers inside each BC)
- Format: "Mermaid (Recommended)" (text-based, version-control friendly, renders natively in GitHub/GitLab — default for README.md in GitHub projects) or "draw.io" (visual editor, richer styling, exportable to PNG/SVG)
Invoke the chosen skill - Use the Skill tool to invoke either mermaid or drawio with the identified BCs, subsystems, interactions, and chosen detail level. When the diagram is destined for a README.md in a GitHub project, default to Mermaid without asking.

Diagram Content Guidelines

Between components (default)

Show BCs, subsystems, and external services — not classes, methods, or fields
Represent each BC as a single node labeled by its responsibility: Orders, Payments, Users
Group BCs into subsystems when they share a domain: subgraph Billing [Orders, Payments, Invoicing]
Focus on interactions between BCs: which boundary calls which boundary, what data flows where
Label arrows with the interaction type when not obvious: -->|REST|, -->|async|, -->|JPA|
Show external dependencies (third-party APIs, databases, message brokers) as separate nodes

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

11d ago First seen · 50 lines · 122 tokens per session scan A 700686061d10

Subscribe to this mod's changes

bce-diagrams is a skill published in the GitHub repository AdamBien/airails (50 stars, last pushed 3d ago), licensed MIT. It adds 122 tokens to every session and 834 once invoked, about $0.0006 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-08-30.

Design and UX Java LLM Planning agents ai bce-design skills

drawio-logical-diagrams

Creates professional logical flow diagrams and logical system architecture diagrams using draw.io XML format (.drawio files). Use when creating: (1) logical flow diagrams showing data/process flow between system components, (2) logical architecture diagrams representing system structure without cloud provider…

giuseppe-trisciuoglio/developer-kit · 133 tokens

aws-drawio-architecture-diagrams

Creates professional AWS architecture diagrams in draw.io XML format (.drawio files) using official AWS Architecture Icons (aws4 library). Use when the user asks for AWS diagrams, VPC layouts, multi-tier architectures, serverless designs, network topology, or draw.io exports involving Lambda, EC2, RDS, or other AWS…

giuseppe-trisciuoglio/developer-kit · 76 tokens

react-code-review

Provides comprehensive code review capability for React applications, validates component architecture, hooks usage, React 19 patterns, state management, performance optimization, accessibility compliance, and TypeScript integration. Use when reviewing React code changes, before merging pull requests, after…

giuseppe-trisciuoglio/developer-kit · 81 tokens

tailwind-css-patterns

Provides comprehensive Tailwind CSS utility-first styling patterns including responsive design, layout utilities, flexbox, grid, spacing, typography, colors, and modern CSS best practices. Use when styling React/Vue/Svelte components, building responsive layouts, implementing design systems, or optimizing CSS workflow.

giuseppe-trisciuoglio/developer-kit · 62 tokens

tailwind-design-system

Skill for creating and managing a Design System using Tailwind CSS and shadcn/ui. Use when defining design tokens, setting up theming with CSS variables, building a consistent UI component library, initializing a design system configuration, or wrapping shadcn/ui components into design system primitives.