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 soulcodex/agentic --skill module-federation-debugginggit 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-debugging)<a href="https://agentmods.dev/skills/soulcodex/agentic/module-federation-debugging"><img src="https://agentmods.dev/badge/skills/soulcodex/agentic/module-federation-debugging/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/soulcodex/agentic/module-federation-debugging"><img src="https://agentmods.dev/badge/skills/soulcodex/agentic/module-federation-debugging.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.00044 | $0.01190 |
| Opus 5.5 | $0.00018 | $0.00476 |
| Sonnet 5.5 | $0.00009 | $0.00238 |
| Haiku 4.5 | $0.00004 | $0.00119 |
Grade A, and why
module-federation-debugging 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Module Federation Debugging Skill
Use this skill when a Module Federation host or remote fails to load, renders a
blank page, hangs in a loading state, throws a RUNTIME-xxx error, has unclear
shared dependency behavior, cannot resolve generated types, fails only in
production, or behaves differently between browser and SSR.
For SSR-specific architecture choices and host/remote creation, also use the
module-federation-ssr skill when it is available. This skill owns the
debugging investigation; the SSR skill owns SSR architecture boundaries.
Step 1 - Name The Failure Boundary
Do not start by changing configuration. First classify the likely boundary:
| Boundary | Common Signals |
|---|---|
| config | missing plugin, wrong plugin, bad expose key, missing async startup |
| producer artifact | stale or missing manifest, remote entry, exposes, stats, types |
| network | 404, 5xx, CORS, DNS, timeout, CDN, gateway, mixed content |
| runtime | RUNTIME-xxx, container missing, script execution failure |
| shared dependency | duplicate React/Vue, wrong singleton, externals conflict |
| type contract | missing @mf-types, producer DTS failure, path mapping issue |
| render | remote loaded but component throws or error boundary trips |
| SSR/hydration | server loads differently than browser, hydration mismatch |
| cache/version | host and remote use different deployed artifact versions |
If the boundary is unclear, read resources/evidence-map.md and collect the minimum facts needed to narrow it.
Step 2 - Collect Evidence In Order
Use this order unless a hard error points to a narrower path:
- Effective host and remote Module Federation config.
- Runtime role: host, remote, or both.
- Rendering mode: CSR, client-only island in SSR app, or true SSR federation.
- Remote declaration, manifest URL, remote entry URL, and requested expose key.
- Browser Network and console evidence.
- Server logs and Node/SSR observability files when SSR is involved.
- Shared dependency versions and singleton policy.
- Generated type artifacts and TypeScript diagnostics.
- Build stats, manifest/snapshot data, and deployment version.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 First seen · 126 lines · 44 tokens per session scan A 3341dab27f66
module-federation-debugging is a skill published in the GitHub repository soulcodex/agentic (10 stars, last pushed 2d ago), licensed MIT. It adds 44 tokens to every session and 1,190 once invoked, about $0.0002 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-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…
agent-debug-ci
Investigate failed scheduled or nightly GitHub Actions runs on the default branch, determine whether the failure is reproducible and repository-owned, implement the smallest evidence-backed fix, validate it, and open a pull request. Use when a failed nightly CI event starts an agent, or when the standard CI or…
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, renderer performance…
guidance-build
Wireit orchestration, build optimization, caching strategies, and build troubleshooting for the Elements monorepo. Use this skill whenever the user asks about Wireit configuration, build tasks, build dependencies, cache invalidation, build performance, adding new build tasks to package.json, cross-package dependency…
agent-inspect
Local evidence debugger and trajectory-test toolkit for TypeScript AI agents. Use when capturing framework-faithful traces, asserting TraceContract/TraceFacts, packaging Evidence v2, or inspecting local runs over read-only MCP (gettracefacts).
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…