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-boundary-remediation)<a href="https://agentmods.dev/rules/lucamezzalira/mfe-skills/mfe-boundary-remediation"><img src="https://agentmods.dev/badge/rules/lucamezzalira/mfe-skills/mfe-boundary-remediation/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-boundary-remediation"><img src="https://agentmods.dev/badge/rules/lucamezzalira/mfe-skills/mfe-boundary-remediation.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.03936 | $0.03936 |
| Opus 5.5 | $0.01574 | $0.01574 |
| Sonnet 5.5 | $0.00787 | $0.00787 |
| Haiku 4.5 | $0.00394 | $0.00394 |
Grade A, and why
mfe-boundary-remediation 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 — 477 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Remediation patterns
Contents
- Rule 1 — Reframing a component as a micro-frontend (or vice versa)
- Rule 2 — Reducing an oversized API surface
- Rule 3 — Removing a cross-boundary import
- Rule 4 — Replacing shared state with events
- Rule 5 — Decoupling deployments
- Rule 6 — Adding graceful fallbacks
- Rule 7 — Consolidating a granular horizontal split
- Governance extension remediation patterns
Version: 1.2 | Skill: reviewing-mfe-boundaries | Source: Building Micro-Frontends (O'Reilly)
Each section maps to one of the eight boundary rules.
Rule 1 — Reframing a component as a micro-frontend (or vice versa)
If a unit named or behaving as a UI component is being integrated as a micro-frontend, the fix is to decide which it actually is:
If it is truly a shared UI primitive (button, form field, layout wrapper): move it to an npm design system package. Remove the runtime integration overhead. It should be a versioned package dependency, not a deployed micro-frontend.
If it is truly a business capability masquerading as a component: rename it to reflect the domain, assign a single team to own it, and ensure it fetches its own data rather than receiving domain objects as props.
If the boundary is ambiguous: run the boundary health check from understanding-mfe-architecture/references/rules.md. If it fails two or more tests, it is in the wrong category.
Rule 2 — Reducing an oversized API surface
Before — container owns context:
<CheckoutMicrofrontend
user={user}
cart={cart}
shippingOptions={shippingOptions}
paymentMethods={paymentMethods}
discountCodes={discountCodes}
/>
After — step 1: identify which props are domain data the micro-frontend should fetch itself.
In this example: shippingOptions, paymentMethods, and discountCodes are checkout domain data. The checkout micro-frontend should retrieve them from its own backend (BFF or API layer), not receive them from the container.
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 · +11 lines · +97 tokens per session 6819b4abbb0e
- 2mo ago First seen · 466 lines · 3,839 tokens per session scan A b94f0cb9ce13
mfe-boundary-remediation is a cursor rule published in the GitHub repository lucamezzalira/mfe-skills (53 stars, last pushed 1mo ago), licensed MIT. It adds 3,936 tokens to every session, about $0.0157 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.