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-ssrgit 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-ssr)<a href="https://agentmods.dev/skills/soulcodex/agentic/module-federation-ssr"><img src="https://agentmods.dev/badge/skills/soulcodex/agentic/module-federation-ssr/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-ssr"><img src="https://agentmods.dev/badge/skills/soulcodex/agentic/module-federation-ssr.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.00048 | $0.01018 |
| Opus 5.5 | $0.00019 | $0.00407 |
| Sonnet 5.5 | $0.00010 | $0.00204 |
| Haiku 4.5 | $0.00005 | $0.00102 |
Grade A, and why
module-federation-ssr 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Module Federation SSR Skill
Use this skill when a Module Federation task involves SSR, hydration, server entries, streamed rendering, Modern.js, Nuxt, Next.js, Vinext, Vite SSR, or server-rendered host/remote contracts.
If the task is a client-rendered Rsbuild MFE with no SSR requirement, use the
regular module-federation skill instead.
For deep runtime debugging, observability reports, production-only failures, or
unclear host/remote ownership, use the module-federation-debugging skill when
it is available, then return here for SSR architecture decisions.
Step 1 - Classify The Rendering Contract
Determine the real rendering mode before editing configuration:
| Mode | Meaning |
|---|---|
| CSR federation | An SSR-capable app loads the remote only in the browser. |
| SSR federation | The host server loads and renders the remote, then the browser hydrates the same graph. |
| Dual producer | A remote publishes browser and Node artifacts for SSR consumers. |
When the user says "SSR support", do not assume true SSR federation. Ask only when local code and deployment config cannot reveal whether the remote must render on the server.
Step 2 - Choose The Implementation Family
Read resources/architecture-matrix.md before choosing or recommending a framework.
Default guidance:
- Use Rsbuild plus
@module-federation/rsbuild-pluginfor new client-rendered React/Vue host and remote applications. - Use Modern.js and
@module-federation/modern-js-v3as the preferred new SSR Module Federation application path when the project can adopt Modern.js. - Use Rslib for remotes that need to publish both browser and Node artifacts.
- Treat Nuxt SSR federation as beta and verify deployment constraints before adopting it.
- Treat Next.js Module Federation as legacy Pages Router maintenance only. Do not recommend it for new App Router SSR architecture.
- Treat Vinext as experimental unless the repository already adopted it and owns the compatibility risk.
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 · 114 lines · 48 tokens per session scan A 27740a1d816c
module-federation-ssr is a skill published in the GitHub repository soulcodex/agentic (10 stars, last pushed 1mo ago), licensed MIT. It adds 48 tokens to every session and 1,018 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
housekeeping
A periodic maintenance pass: backlog hygiene, docs/changelog currency, release check, worktree/branch prune, dependency triage, issue triage, CI/test green, drift audits.
create-issue
Draft and submit a GitHub issue from a user idea or bug description, with bilingual body and correct labels.
issue-creator
A guide for turning unclear user feedback from text, chat excerpts, or screenshots into a focused GitHub issue, a tracked software-work item. It preserves the original request and separates evidence from information that is still unknown.
status
Surfaces the current state of work in gflow-cli. Three variants at different levels of detail: full state (status), next task only (next), active plan identity (active). All variants run scripts/dev/activeplan.py and filter its output to the requested detail level.
write-workflows
Author Mendix workflows in MDL — user tasks, decisions, parallel splits, jumps, waits and boundary events, with CREATE, ALTER and DROP. Use when building a business process with human steps, timers or parallel branches.
team-workflow
Design the team's operating rhythm — task management, collaboration rituals, and tooling. Use when the day-to-day cadence needs structure. For a time-boxed sprint, use design-sprint-plan.