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.
npx skills add xiaohei-info/oh-my-multica --skill software-design-lifecycle-solution-design-biz-arch-diagramminggit clone --depth 1 https://github.com/xiaohei-info/oh-my-multicaWrote 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/skills/xiaohei-info/oh-my-multica/software-design-lifecycle-solution-design-biz-arch-diagramming)<a href="https://agentmods.dev/skills/xiaohei-info/oh-my-multica/software-design-lifecycle-solution-design-biz-arch-diagramming"><img src="https://agentmods.dev/badge/skills/xiaohei-info/oh-my-multica/software-design-lifecycle-solution-design-biz-arch-diagramming/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/skills/xiaohei-info/oh-my-multica/software-design-lifecycle-solution-design-biz-arch-diagramming"><img src="https://agentmods.dev/badge/skills/xiaohei-info/oh-my-multica/software-design-lifecycle-solution-design-biz-arch-diagramming.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00057 | $0.11722 |
| Opus 5 | $0.00028 | $0.05861 |
| Sonnet 5 | $0.00011 | $0.02344 |
| Haiku 4.5 | $0.00006 | $0.01172 |
Grade A, and why
software-design-lifecycle-solution-design-biz-arch-diagramming 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 12d 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.
How it starts
The opening of the file, as written. The whole thing — 777 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Solution Design Business Architecture Diagramming
Overview
This skill now directly contains the merged specialist doctrine that previously lived in the legacy business-solution architecture skill. Valuable content is preserved and relocated here rather than being wrapped indirectly.
Integrated Legacy Specialist Doctrine (Preserved and Merged)
Business Solution Architecture Lifecycle
Overview
这是 architect profile 私域下的业务解决方案架构设计与绘图 skill。
它不是单纯的“怎么把图画好看”，也不是纯技术架构图规范；它服务于软件架构设计生命周期中的解决方案设计阶段：
- 需求调研已完成并经相关方 review
- 需要把业务问题推进为可评审、可沟通、可进入后续技术设计的中层方案产物
- 产物通常包括：业务流程、领域模型、业务解决方案架构图、风险与治理说明、实施节奏说明
本 skill 的目标有两层，而且两层都必须保留：
-
完整保留业务解决方案架构图的绘图方法学细节
- 业务语境解析
- 架构模式识别
- 视角分层与叙事结构
- 业务域着色
- 语义节点映射
- 关系连线映射
- 布局编排与工具选择
- 一致性检查
-
叠加 architect 角色在解决方案设计阶段必须做的架构审查门
- 生命周期进入条件
- 方案调研与复用判断
- 外部依赖可靠性 / 降级 / 兜底 / 隔离
- 核心业务状态闭环
- 风险与治理控制点
- 实施节奏与最小闭环里程碑
核心原则： 业务解决方案架构图不是装饰性插图，而是把“已确认的业务问题”压缩成“可进入后续技术设计的中层方案结构”的正式架构产物。
0. 生命周期定位（architect 增强，不替代绘图细节）
0.1 所处阶段
本 skill 用于：
- 业务需求调研文档与相关反馈已确认后
- 技术方案设计（概要设计 / 详细设计）之前
它属于：
- 解决方案设计文档的一部分
而不是：
- 技术架构图
- 模块内部详细设计
- 部署拓扑图
- 运维手册
0.2 前置输入（缺一不可）
在正式画图前，至少应已有：
- 已确认的需求背景
- 系统现状 / 当前痛点
- 目标效果 / 业务收益
- 成功指标或 ROI 信号
- 非目标 / 边界约束
- 若适用，已完成的成熟方案调研与复用判断
如果这些输入缺失，不要直接画图，应退回问题澄清。
0.3 该图必须额外回答的 architect 问题
除了“怎么画”，还必须回答：
- 这个方案依赖哪些外部系统、上下游系统或第三方能力？
- 哪些依赖必须按不可靠依赖处理？异常时如何降级、兜底或隔离？
- 核心业务状态是否形成闭环？正常、异常、回退路径是否明确？
- 哪些高风险点必须在图中显式出现治理 / 控制位？
- 最小可交付闭环是什么？哪些能力属于后续阶段？
1. 能力边界（Agent 自检）
本 Skill 产出的是业务解决方案架构图——回答的问题是：
「为了支撑这个业务场景，系统方案长什么样？谁参与、什么流程、数据如何流转、解决了什么痛点？」
1.1 适用场景
- 需求评审会上对齐业务与技术的全局理解
- 项目启动会上展示系统方案轮廓
- 招投标/立项材料中的架构插图
- 业务方理解系统如何支撑其操作流程
- 解决方案设计文档中的中层方案图
- 在进入技术方案设计前，对业务方案进行结构化澄清与 review
1.2 不适用场景（必须拒绝并提示用户）
- 纯技术实现细节图（微服务调用链、类图、ER图、部署拓扑）
- 纯业务组织图（部门分工、RACI、汇报线）
- 纯商业模式图（价值链、盈利模型）
- 模块内部详细设计图（字段级 schema、adapter 级执行路径、连接/认证编排）
- 物理架构 / 网络拓扑 / 运维部署图
1.3 图种职责边界（architect 必须显式区分）
- 业务流程图：说明角色、步骤与处理顺序
- 领域模型图：说明业务对象、边界与语义关系
- 业务解决方案架构图：说明用户入口、中间处理环节、外部系统与输出结果之间的整体方案关系
- 系统架构图：说明内部子系统、外部依赖、通信关系与边界条件
- 技术架构图：说明具体技术栈、引擎、中间件、数据存储与执行路径
- 状态机 / 流程 / 时序补图：说明状态闭环、异常路径、回退路径与运行分支
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 777 lines · 57 tokens per session scan A 9154a2d775db
software-design-lifecycle-solution-design-biz-arch-diagramming is a skill published in the GitHub repository xiaohei-info/oh-my-multica (26 stars, last pushed 5d ago), licensed MIT. It adds 57 tokens to every session and 11,722 once invoked, about $0.0003 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.
Other skills, from other repositories
frontend-design
Produce intentional, responsive, accessible UI work and perform visual QA instead of generic component assembly.
tutti-ui-system
Use when working with @tutti-os/ui-system components, replacing local UI with shared components, querying component ids or metadata, promoting UI into shared base or business components, or maintaining UI-system storyboard inventory.
mcp-host-styling-integration
Integrates MCP App UI with host theming system. Applies host CSS variables, handles onhostcontextchanged, safe area insets, display mode detection, and fullscreen configuration.
ux-design
Create comprehensive UX design with user flows, wireframes, and design systems.
accessibility-a11y
Semantic HTML, keyboard navigation, focus states, ARIA labels, skip links, and WCAG contrast requirements. Use when ensuring accessibility compliance, implementing keyboard navigation, or adding screen reader support.
tailwind-shadcn
Tailwind CSS utility patterns with shadcn/ui component usage, theming via CSS variables, and responsive design. Use when styling components, installing shadcn components, implementing dark mode, or creating consistent design systems.