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-tech-overview-system-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-tech-overview-system-arch-diagramming)<a href="https://agentmods.dev/skills/xiaohei-info/oh-my-multica/software-design-lifecycle-tech-overview-system-arch-diagramming"><img src="https://agentmods.dev/badge/skills/xiaohei-info/oh-my-multica/software-design-lifecycle-tech-overview-system-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-tech-overview-system-arch-diagramming"><img src="https://agentmods.dev/badge/skills/xiaohei-info/oh-my-multica/software-design-lifecycle-tech-overview-system-arch-diagramming.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
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 →
- high Memory Poisoning · line 473 Skill manipulates agent memory, state, or stored context. Memory corruption can alter personality, override safety rules, or cause unpredictable behavior.Fix: Protect agent memory and state from modification by untrusted content. Use read-only memory for critical instructions and validate all state changes.
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.00049 | $0.10258 |
| Opus 5.5 | $0.00020 | $0.04103 |
| Sonnet 5.5 | $0.00010 | $0.02052 |
| Haiku 4.5 | $0.00005 | $0.01026 |
Grade A, and why
software-design-lifecycle-tech-overview-system-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 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.
How it starts
The opening of the file, as written. The whole thing — 773 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Technical Overview System Architecture Diagramming
Overview
This skill now directly contains the merged specialist doctrine that previously lived in the legacy system-architecture skill.
Integrated Legacy Specialist Doctrine (Preserved and Merged)
System Architecture Diagramming
Overview
This is the architect-private skill for drawing and reviewing 系统架构图 in the 概要设计 stage.
This skill intentionally preserves the full drawing-detail layer from the system-architecture-diagram spec instead of compressing it away. It is meant to strengthen architect execution, not merely restate high-level principles.
Its role in the architecture lifecycle is anchored in the local source note 软件架构设计生命周期:
- 功能架构图 负责把设计层、运行层、数据底座与运营支撑拆开。
- 系统架构图 负责交代内部子系统、外部依赖、通信关系与边界条件。
- 技术架构图 负责把系统进一步压到具体技术栈、引擎、中间件、数据存储与执行路径。
Core principle: 系统架构图 belongs to overview design, so it should explain subsystem structure, dependency boundaries, and collaboration relationships — not merely list functions, not collapse into流程时序, and not yet dive into full technical-stack implementation detail.
This skill exists because many so-called “系统架构图” fail in one of four ways:
- they are really 功能清单/功能分层图, so they say what the system should do but not what subsystems exist or how boundaries are controlled
- they are really 流程图/时序图, so they show time order instead of stable structure
- they are really 技术架构图, so they jump too early into concrete middleware, engine, host, container, or code-carrier detail
- they throw away the detailed visual grammar, so future diagrams lose consistency in colors, shapes, boundaries, and line semantics
Use this skill to produce a diagram that is abstract enough for 概要设计, but detailed enough in drawing grammar to guide later technical architecture, interface design, deployment design, and review.
When to Use
Use when:
- the user asks for 系统架构图、概要设计中的系统架构图、子系统架构图、系统边界图
- you need one picture to explain what lives inside the system, what stays outside, and how the two sides collaborate
- a design doc must show internal subsystem decomposition plus external dependencies
- the team is mixing 功能视角, 系统视角, 技术视角, and 流程视角 and needs a clean separation
- you need to review whether an existing “架构图” is actually a proper system-architecture artifact
- you need the full visual spec preserved: primitive vocabulary, color semantics, shape rules, line semantics, boundary rules, layout modes, anti-pattern checks, and tool adaptation
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.
- 1mo ago First seen · 773 lines · 49 tokens per session scan A 4ce782c2e414
software-design-lifecycle-tech-overview-system-arch-diagramming is a skill published in the GitHub repository xiaohei-info/oh-my-multica (37 stars, last pushed 17d ago), licensed MIT. It adds 49 tokens to every session and 10,258 once invoked, about $0.0002 per session on Opus 5.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
wireframe
Produce low-fidelity black-and-white UI wireframes as SVGs or viewer pages. Use when asked to wireframe, sketch a screen, draft a layout, make a low-fi mockup, or publish wireframes.
design-critique
Give a structured product design critique — user job clarity, hierarchy, affordance, error states, accessibility, and consistency — focused on what to change, in what order, and why.
paperclip-capsules
Generate, implement, or review Paperclip capsule visuals. Use for capsule art, agent capsules, heartbeat status capsules, identicons, capsule banks, or brand-usage validation.
frontend-design
Produce intentional, responsive, accessible UI work and perform visual QA instead of generic component assembly.
ui-mockup
Create UI mockups at three fidelity levels — ASCII wireframes for quick iteration, standalone HTML mockups for delivery with requirements, and live prototypes for interaction testing.
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.