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-functional-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-functional-arch-diagramming)<a href="https://agentmods.dev/skills/xiaohei-info/oh-my-multica/software-design-lifecycle-tech-overview-functional-arch-diagramming"><img src="https://agentmods.dev/badge/skills/xiaohei-info/oh-my-multica/software-design-lifecycle-tech-overview-functional-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-functional-arch-diagramming"><img src="https://agentmods.dev/badge/skills/xiaohei-info/oh-my-multica/software-design-lifecycle-tech-overview-functional-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.00050 | $0.04977 |
| Opus 5 | $0.00025 | $0.02488 |
| Sonnet 5 | $0.00010 | $0.00995 |
| Haiku 4.5 | $0.00005 | $0.00498 |
Grade A, and why
software-design-lifecycle-tech-overview-functional-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 — 609 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Technical Overview Functional Architecture Diagramming
Overview
This skill now directly contains the merged specialist doctrine that previously lived in the legacy system-functional-architecture skill.
Integrated Legacy Specialist Doctrine (Preserved and Merged)
System Functional Architecture Diagramming
Overview
This is the architect-private skill for drawing and reviewing 系统功能架构图 in the 概要设计 stage.
It strengthens a generic diagramming meta-spec with the architecture-lifecycle requirement that a functional architecture diagram must answer, at minimum:
- 系统建设目标是什么
- 要有哪些功能
- 这些功能如何分层
- 哪些功能是核心闭环，哪些是支撑能力
- 功能之间如何协作，但不过早坠入技术实现细节
Core principle: 系统功能架构图 belongs to overview design, so it should explain capability structure and layering, not code structure, deployment topology, or runtime sequence detail.
This skill exists because many so-called “功能架构图” fail in one of two ways:
- they are only a feature list with boxes, but no layering logic or system goal
- they collapse into technical architecture, process flow, or deployment views and lose their functional-design role
Use this skill to produce a diagram that is abstract enough for 概要设计, but concrete enough to guide later system architecture, technical architecture, and detailed design.
Canonical full-fidelity drawing spec:
references/universal-diagramming-spec-full.md
Important preservation rule:
- the full drawing/detail content from the source publication is preserved there verbatim
- this umbrella skill is an architect usage layer on top of that source, not a replacement for it
- when any summary here conflicts in detail, completeness, wording, or emphasis with the full reference, treat the full reference as authoritative
- do not compress, rewrite away, or omit the drawing-specific details from the full reference when using this skill for real diagram production
When to Use
Use when:
- the user asks for 系统功能架构图、功能分层图、概要设计中的功能架构图
- you are in the 概要设计 stage and must show what the system does before showing how it is implemented
- a solution/design doc needs one picture to explain major functional modules and their relationships
- the team is mixing business solution view, functional view, system view, and technical view and needs clean separation
- you need to review whether an existing architecture diagram is truly a functional-architecture artifact
What ships with it
2 files 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 · 609 lines · 50 tokens per session scan A 376bbb8419ed
software-design-lifecycle-tech-overview-functional-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 50 tokens to every session and 4,977 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.