Borrowing it
Nothing to install: this file belongs to LedgerHQ/ledger-live. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/LedgerHQ/ledger-live/develop/.agents/skills/mvvm-architecture/SKILL.mdgit clone --depth 1 https://github.com/LedgerHQ/ledger-liveWrote 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/ledgerhq/ledger-live/mvvm-architecture)<a href="https://agentmods.dev/skills/ledgerhq/ledger-live/mvvm-architecture"><img src="https://agentmods.dev/badge/skills/ledgerhq/ledger-live/mvvm-architecture/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/ledgerhq/ledger-live/mvvm-architecture"><img src="https://agentmods.dev/badge/skills/ledgerhq/ledger-live/mvvm-architecture.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.00092 | $0.01319 |
| Opus 5.5 | $0.00037 | $0.00528 |
| Sonnet 5.5 | $0.00018 | $0.00264 |
| Haiku 4.5 | $0.00009 | $0.00132 |
Grade A, and why
mvvm-architecture 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 today.
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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MVVM Architecture
Scope
apps/<app>/src/mvvm/ holds two kinds of code:
- App screens composing
@features/*: the screen, its routing, store and analytics wiring, and the adapters that connect a feature package to app internals. - App-only features: code that depends on app internals and that no other app or flow reuses.
src/mvvm is not the default home of new code. Decide placement with
structure-flow first: business-aware UI and journeys go to
features/, data access to domain/, generic code to shared/. The app folder keeps only what
composes them.
Example: desktop src/mvvm/features/Contacts/ renders @features/flow-contacts and passes it
app-side adapters (useContactsCurrencySelectionAdapter, useContactsAddressValidationAdapter).
The contacts journey itself lives in the flow package.
The ViewModel pattern is not apps-only: it is also mandatory in every
features/flow package. The folder structure below is apps-only; the anatomy of a flow package
belongs to the flow-package skill.
Folder Structure
Applies to apps/*/src/mvvm/ only.
src/mvvm/
├── features/
│ └── FeatureName/
│ ├── __integrations__/ ← mandatory integration tests
│ ├── components/ ← UI reused across this feature's screens
│ ├── screens/ ← individual screen folders
│ ├── hooks/ ← feature-scoped hooks, adapters to app internals
│ └── utils/ ← feature-scoped utilities
├── components/ ← UI shared by several app features
├── hooks/
└── utils/
Place each element in the closest folder matching its reuse scope: screen-specific building blocks
stay in the screen folder, feature-level ones in FeatureName/components/, app-wide ones in
src/mvvm/components/. An element several apps need belongs in a package, not here.
Component & File Patterns
In src/mvvm/:
- Each component in its own folder with
index.tsxas entry. - ViewModel hooks always named
use<ComponentName>ViewModel.ts. - Support files alongside:
types.ts,styles.ts. - Use List / Detail naming for multi-view workflows.
- Utilities stay in
utils/, separate from component folders.
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.
- today Changed · +1 lines f3f501c8c0fe
- 2d ago Changed · +31 lines · +44 tokens per session 42c6b8726e1e
- 2mo ago First seen · 97 lines · 48 tokens per session scan A 955ed85af0de
mvvm-architecture is a skill published in the GitHub repository LedgerHQ/ledger-live (624 stars, last pushed yesterday), licensed MIT. It adds 92 tokens to every session and 1,319 once invoked, about $0.0004 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
winapp-maui
Package and sign .NET MAUI Windows apps with winapp: publish the Windows head first, then point packaging at the resolved resizetizer manifest. Use for a MAUI MSIX or signed unpackaged build, MAUI packaging in CI, or 'manifest contains unresolved placeholders' errors from winapp package.
android-pentest
A guide for authorized security testing of Android apps, covering APK inspection, runtime testing, traffic capture, code review, and function hooking. An APK is the installable package used by an Android app.
apple-search-ads
When the user wants to set up, optimize, or scale Apple Search Ads (ASA) campaigns — including keyword bidding, match types, campaign structure, Creative Product Sets, CPP routing, and ROAS optimization. Use when the user mentions "Apple Search Ads", "ASA", "Search Ads", "Search tab ads", "Today tab ads", "CPT"…
Swift Performance Optimization Skill
Use when investigating measured Swift or Apple-platform regressions in CPU, memory, launch, scrolling, animation hitches, image processing, energy, networking, or concurrency, or when designing performance tests and Instruments experiments. Do not use for speculative micro-optimization, ordinary refactoring, or a…
mobiai-mobile-tdd
You MUST use this before writing any implementation code for a mobile feature, bug fix, refactor, or behavior change. Tests come before implementation — no exceptions.
mobiai-mobile-verification
You MUST use this before declaring any mobile work done, fixed, green, or ready — and before committing, pushing, or opening a PR. No completion claim may be made without fresh verification evidence from this session.