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 agentmods add skills/soulcodex/agentic/module-federationnpx skills add soulcodex/agentic --skill module-federationgit clone --depth 1 https://github.com/soulcodex/agenticWrote 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/soulcodex/agentic/module-federation)<a href="https://agentmods.dev/skills/soulcodex/agentic/module-federation"><img src="https://agentmods.dev/badge/skills/soulcodex/agentic/module-federation.svg" alt="Measured on agentmods" 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.00051 | $0.01403 |
| Opus 5 | $0.00026 | $0.00701 |
| Sonnet 5 | $0.00010 | $0.00281 |
| Haiku 4.5 | $0.00005 | $0.00140 |
Grade A, and why
module-federation 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 2d 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 — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Module Federation Skill
Use this skill when adding client-rendered Module Federation, reviewing host/remote contracts, debugging federated loading, or fixing type generation and shared dependency issues.
For SSR federation, hydration failures, server entries, Modern.js, Nuxt,
Next.js, Vinext, or Vite SSR, use the module-federation-ssr skill when it is
available. If only this skill is available, keep the work conservative: prefer
Rsbuild for non-SSR federation, treat Modern.js as the preferred SSR app path,
use Rslib for dual browser/server remote artifacts, treat Nuxt SSR federation
as beta, and treat Next.js Module Federation as legacy Pages Router maintenance
only.
For deep runtime debugging, production-only failures, observability reports, or
unclear host/remote ownership, use the module-federation-debugging skill when
it is available.
Step 1 - Inspect The Project
Read the project root before changing files:
package.jsonpnpm-lock.yamlwhen dependency versions matterrsbuild.config.*module-federation.config.*tsconfig*.json- app entry points and route registration that import remotes or exposed modules
If the project has no Rsbuild, Rspack, Webpack, Modern.js, Next, Vite, or related build config, treat it as a new client-rendered project and recommend the official scaffold:
npm create module-federation@latest
For new in-repo implementation, prefer Rsbuild unless local project instructions name another framework-owned build system. Do not retrofit true SSR federation from this skill; route that work to SSR-specific guidance first.
Step 2 - Determine The Role
Classify the app before editing config:
| Role | Meaning |
|---|---|
consumer |
Loads modules from remote apps through remotes. |
provider |
Exposes modules to other apps through exposes. |
both |
Publishes exposes and consumes remotes. |
Use the package name as the starting app name, converted to snake_case. Module Federation app names must not contain hyphens.
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.
- 2d ago First seen · 201 lines · 51 tokens per session scan A 2d01e1fae6b5
module-federation is a skill published in the GitHub repository soulcodex/agentic (10 stars, last pushed yesterday), licensed MIT. It adds 51 tokens to every session and 1,403 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
agent-upkeep
Perform one small, scoped maintenance improvement to the Elements monorepo and open a single reviewable pull request. Use this skill for scheduled or unattended upkeep runs that improve unit test coverage for one file, fix one behavioral bug in one module, or move one off ESLint rule toward enforcement to reduce…
guidance-webgpu-performance
Diagnose and improve browser WebGPU rendering performance, including frame pacing, draw and state-submission overhead, buffer uploads, shaders, and JavaScript work on the render critical path. Use for slow or stuttering GPU-backed interfaces, rendering regressions, CPU/GPU bottleneck analysis, or renderer performance…
authoring-tests
Write and run automated tests for Elements components including unit, accessibility, visual, SSR, and lighthouse tests. Use this skill whenever the user wants to write, create, update, or debug test files (.test.ts, .test.axe.ts, .test.visual.ts, .test.ssr.ts, .test.lighthouse.ts). Also trigger when the user asks…
troubleshooting
Diagnose and resolve common issues including test failures, build errors, performance regressions, and development environment problems. Use this skill whenever the user reports something broken, failing, timing out, hanging, or producing unexpected results. Trigger on test failures (elementIsStable timeouts, flaky…
doctor
Use when the capstone docs area needs a consistency check or repair - torn writes, done markers without ledger entries, voided plan approvals, index rows pointing at missing files, absorption gaps - reports findings with their owning rules, then applies only the repairs the user approves.
logging-observability-standards
When setting up telemetry, debugging distributed systems, or standardizing application output.