Borrowing it
Nothing to install: this file belongs to lucamezzalira/mfe-skills. 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/lucamezzalira/mfe-skills/main/AGENTS.mdgit 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/instructions/lucamezzalira/mfe-skills/agents-md)<a href="https://agentmods.dev/instructions/lucamezzalira/mfe-skills/agents-md"><img src="https://agentmods.dev/badge/instructions/lucamezzalira/mfe-skills/agents-md/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/instructions/lucamezzalira/mfe-skills/agents-md"><img src="https://agentmods.dev/badge/instructions/lucamezzalira/mfe-skills/agents-md.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.00932 | $0.00932 |
| Opus 5 | $0.00466 | $0.00466 |
| Sonnet 5 | $0.00186 | $0.00186 |
| Haiku 4.5 | $0.00093 | $0.00093 |
Grade A, and why
mfe-skills AGENTS.md 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 12d 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MFE Boundary Governance
Micro-frontend architecture skills by Luca Mezzalira (mfe-skills v1.0.0). Full reference: https://github.com/lucamezzalira/mfe-skills
Apply these rules when reviewing or generating code that crosses a team deployment boundary: shell mounting, cross-MFE communication, remote loading, or contract design.
Essential: Pair this file with project-specific facts in the same AGENTS.md (which team owns which MFE, toolchain, routes.json location, known exceptions). Without that context, advice stays generic.
Boundary health check
Before generating MFE code, verify:
- Is the API surface minimal, fewer than 5 props to the container?
- Is the MFE context-aware, does it retrieve its own data given minimal input?
- Is it less extensible than a component, not designed for reuse across domains?
- Is it coarse-grained, not fine enough to require constant coordination?
- Can it deploy without coordinating with other teams?
- Does it have a graceful fallback if it fails to load?
- Does a single team own it end-to-end?
If any answer is no, the boundary needs to be revisited before implementation.
The eight boundary rules
| Rule | Principle | Violation signals |
|---|---|---|
| 1 - Business subdomain | One MFE = one business capability owned by one team | Named after UI elements (Header, Sidebar), used across unrelated domains |
| 2 - Minimal API surface | Max ~5 props, identifiers only, no domain objects | Props like user, cart, order; shell fetching data for the MFE |
| 3 - Hides implementation | No cross-MFE imports; each MFE owns its data layer | import { x } from '@org/other-mfe/...'; path aliases masking cross-boundary imports |
| 4 - Events not shared state | Platform bus to shell; domain events peer-to-peer only; no shared stores | Shared Redux/Zustand; window.__mfe_*; shell listening to catalog:* / checkout:* |
| 5 - Independent deployment | No versioned remote URLs; no CI coupling | remotes: { checkout: '...@/v3.2.1/remoteEntry.js' }; CI needs: across MFE pipelines |
| 6 - Isolates failure | ErrorBoundary in shell at every mount; fallbacks in shell | No boundary; fallback only inside MFE; unhandled loadRemoteModule rejection |
| 7 - Coarse-grained | Shell first URL segment via manifest; MFE owns sub-routes | Shell routes like /catalog/product/:id; shell domain event handlers |
| 8 - Single team ownership | One team in CODEOWNERS per MFE | Multiple teams per MFE; no deployment owner |
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.
- 12d ago First seen · 62 lines · 932 tokens per session scan A 0746241cc772
mfe-skills AGENTS.md is an instructions file published in the GitHub repository lucamezzalira/mfe-skills (51 stars, last pushed 17d ago), licensed MIT. It adds 932 tokens to every session, about $0.0047 per session on Opus 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 instructions, from other repositories
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).