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 j4flmao/agent-skills --skill micro-frontendsgit clone --depth 1 https://github.com/j4flmao/agent-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/skills/j4flmao/agent-skills/micro-frontends)<a href="https://agentmods.dev/skills/j4flmao/agent-skills/micro-frontends"><img src="https://agentmods.dev/badge/skills/j4flmao/agent-skills/micro-frontends/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/j4flmao/agent-skills/micro-frontends"><img src="https://agentmods.dev/badge/skills/j4flmao/agent-skills/micro-frontends.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.00000 | $0.00602 |
| Opus 5 | $0.00000 | $0.00301 |
| Sonnet 5 | $0.00000 | $0.00120 |
| Haiku 4.5 | $0.00000 | $0.00060 |
Grade A, and why
micro-frontends 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 7d 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 — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Micro-Frontends (MFE)
1. Skill Context
Focus: Scaling frontend development across multiple independent teams, decoupling monolithic SPAs (React/Vue/Angular), and continuous delivery for UI. Triggers: micro-frontends, module-federation, spa, architecture, web-components.
2. The Monolithic SPA Problem
At enterprise scale, a single React repository (Monolith) becomes a bottleneck.
- 50 developers trying to merge into the same
package.json. - A 10-minute CI/CD build time.
- The Marketing team cannot deploy a typo fix without dragging the heavy E-Commerce codebase with them.
Micro-frontends apply the microservices philosophy to the browser. The UI is assembled from independent fragments maintained by different teams.
3. Implementation Strategies
A. Webpack Module Federation (Run-time Integration)
The Modern Standard. Allows a JavaScript application to dynamically load code from another application at runtime.
- Host App (App Shell): Handles routing, authentication, and the global layout (Sidebar, Header).
- Remote App (e.g., Checkout Team): Exposes its
CheckoutComponent. The Host dynamically imports it. - Pros: Shared dependencies (React is only loaded once). Seamless UX.
- Cons: High coupling in tooling. Requires Webpack 5 (or Vite equivalents).
B. Web Components (DOM Integration)
Teams build their fragments using framework-agnostic Web Components (<checkout-button></checkout-button>).
- Pros: Tech-agnostic. The Host can be Angular, the Remote can be React.
- Cons: Passing complex data structures (objects/functions) across DOM attributes is clunky.
C. IFrames (Isolation Integration)
The Legacy/Nuclear Option.
- Pros: Absolute CSS and JS isolation. Zero chance of a memory leak in the Remote crashing the Host.
- Cons: Terrible UX, routing nightmares, slow performance, impossible to create overlapping overlays (like a global modal).
4. Architectural Anti-Patterns
- The "Shared State" Trap: Trying to use a global Redux store across 5 micro-frontends. If MFE A changes the Redux structure, MFE B crashes. MFEs should communicate via standard DOM Events (
CustomEvent) or query parameters, maintaining minimal shared state. - CSS Bleeding: If the Checkout MFE defines
.btn { color: red; }, it will globally override the Host's CSS. MFEs must enforce CSS Modules, Styled Components, or Shadow DOM to scope their styles. - Dependency Bloat: If Team A uses React 17, Team B uses React 18, and Team C uses Vue, the user downloads 3 MB of frameworks. Technology diversity is a theoretical benefit of MFEs, but a practical nightmare. Enforce a unified tech stack at the enterprise level.
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.
- 7d ago First seen · 39 lines · 0 tokens per session scan A 44f7fac1759e
micro-frontends is a skill published in the GitHub repository j4flmao/agent-skills (23 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 602 tokens. 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-05.
Other skills, from other repositories
visual-ralph
Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ultragoal with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
create-site
Creates a new Power Pages code site (SPA) using React, Angular, Vue, or Astro. Guides through the full process from initial concept to deployed site: requirements discovery, scaffolding, component planning, design, implementation, validation, and deployment. Use when the user wants to create, build, or scaffold a new…
prototype-web
A clickable, high-fidelity web product prototype with navigation, a hero section, feature cards, steps, social proof, and optional pricing. It is designed to resemble a finished landing page while remaining a prototype.
menu-transitions-rtl
Animate react-horizontal-scrolling-menu scrolling and build right-to-left menus: noPolyfill defaults to true since v8, so transitionDuration (default 500), a custom-easing-function transitionBehavior, and per-call ScrollOptions { duration, boundary } on scrollToItem/scrollNext/scrollPrev are silently ignored unless…