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.
git clone --depth 1 https://github.com/lucamezzalira/mfe-skillsWrote 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/rules/lucamezzalira/mfe-skills/mfe-architecture-decisions)<a href="https://agentmods.dev/rules/lucamezzalira/mfe-skills/mfe-architecture-decisions"><img src="https://agentmods.dev/badge/rules/lucamezzalira/mfe-skills/mfe-architecture-decisions/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/rules/lucamezzalira/mfe-skills/mfe-architecture-decisions"><img src="https://agentmods.dev/badge/rules/lucamezzalira/mfe-skills/mfe-architecture-decisions.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.02168 | $0.02168 |
| Opus 5.5 | $0.00867 | $0.00867 |
| Sonnet 5.5 | $0.00434 | $0.00434 |
| Haiku 4.5 | $0.00217 | $0.00217 |
Grade A, and why
mfe-architecture-decisions 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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Micro-frontends decisions framework
Contents
- Decision 1 — Define: horizontal or vertical split?
- Decision 2 — Compose: how does the shell assemble micro-frontends?
- Decision 3 — Route: how does the application direct users between views?
- Decision 4 — Communicate: how do micro-frontends exchange data?
- Operational guardrails (cross-cutting)
- Decisions framework summary
Version: 1.2 | Skill: understanding-mfe-architecture | Source: Building Micro-Frontends (O'Reilly)
The decisions framework is composed of four areas that must be resolved upfront because each one constrains the next:
- Define — horizontal or vertical split?
- Compose — client-side or server-side?
- Route — client-side or server-side?
- Communicate — event emitter, custom events, web storage, query strings?
These decisions are not independent — composition constrains routing, and split strategy constrains communication. The table at the end of this file shows the valid combinations.
Decision 1 — Define: horizontal or vertical split?
Vertical split: one micro-frontend per view or group of views. Each team owns a complete business domain end-to-end — authentication, catalog, checkout. The micro-frontend owns all the routes under its domain.
- Closer to a traditional SPA or server-side rendering approach
- Each team has full autonomy — fewer cross-team coordination points
- Better fit for teams new to micro-frontends
- Recommended as the starting point for most organisations
Horizontal split: multiple micro-frontends composing the same view. Multiple teams share responsibility for parts of the same page.
- Requires more discipline and governance — without it, proliferation of micro-frontends creates a distributed monolith
- Higher granularity → higher coupling → context leakage risk
- Requires upfront investment in a solid development experience (local composition, testing across teams)
- Better fit for teams experienced with micro-frontends and with strong automation
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 Changed · +9 lines · +77 tokens per session 32f9e88d308c
- 2mo ago First seen · 180 lines · 2,091 tokens per session scan A 3fb8286c26d7
mfe-architecture-decisions is a cursor rule published in the GitHub repository lucamezzalira/mfe-skills (53 stars, last pushed 1mo ago), licensed MIT. It adds 2,168 tokens to every session, about $0.0087 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 cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).
control-plane-descriptors
Control plane descriptor and instance implementation patterns.