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/structure-flow/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/structure-flow)<a href="https://agentmods.dev/skills/ledgerhq/ledger-live/structure-flow"><img src="https://agentmods.dev/badge/skills/ledgerhq/ledger-live/structure-flow/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/structure-flow"><img src="https://agentmods.dev/badge/skills/ledgerhq/ledger-live/structure-flow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00118 | $0.01436 |
| Opus 5.5 | $0.00047 | $0.00574 |
| Sonnet 5.5 | $0.00024 | $0.00287 |
| Haiku 4.5 | $0.00012 | $0.00144 |
Grade A, and why
structure-flow 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Structure and flow
Place each concern in the lowest layer that can own it. New code goes in the layers; apps/*/src/mvvm
only holds app screens composing @features/* and app-only code. The layer model, the legacy libs/
status and the import rules live in the architecture guide.
Decide the layer: first yes wins
Ask in order and stop at the first yes.
- Build or test tooling with no business knowledge?
support/<name>, taken as a devDependency. Mocks and fixtures of a domain stay in that domain package. - Zero business meaning, would compile at any company?
shared/<name>. - The business noun itself: its schema, rules, reads?
domain/entity/<name>. Fetching or mutating it?domain/api/<name>, injecting endpoints into a base of@shared/api-services. - Knows the business, serves several features, owns no journey?
features/platform/<name>. - The user sees it and walks through it, entry to exit?
features/flow/<use-case>. - None of the above:
apps/<app>, for final composition, screens, routes, store and telemetry.
Debug tooling embedded in the apps is a side scope, devtools/: see devtools.
Examples per question and the traps between neighbours: references/layers.md.
What each layer may hold
| Layer | Holds | Never |
|---|---|---|
apps/<app> |
Screens, global routing, store, analytics host, observability, glue | Business logic, schemas, entities, slices |
features/flow |
One journey: business-aware UI, flow state, local routing | Another journey, app screen composition |
features/platform |
Hooks, selectors, NFR rules, React glue, UI shared by several flows | Screens, global routing, single-flow internals, a flow |
domain/entity |
Zod schema, inferred type, defaults, mocks, selectors, slice | React, network calls, feature state |
domain/api |
Endpoints, wire schemas, transforms, cache tags, RTK Query hooks | UI, app composition |
shared |
Generic primitives, Redux tooling, generic UI in shared/ui-* |
Business vocabulary (wallet, account, coin), junk drawers |
support |
Test, TypeScript, lint and format configuration | Runtime code |
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.
- today Changed · -20 lines · +52 tokens per session d75709a8d519
- 8d ago Changed 97d5054d31da
- 29d ago Changed bf72cb40cf41
- 1mo ago First seen · 118 lines · 66 tokens per session scan A 3dbdaa31e858
structure-flow is a skill published in the GitHub repository LedgerHQ/ledger-live (624 stars, last pushed yesterday), licensed MIT. It adds 118 tokens to every session and 1,436 once invoked, about $0.0005 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-09-22.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…