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.
git clone --depth 1 https://github.com/vibeeval/vibecosystemWrote 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/agents/vibeeval/vibecosystem/micro-frontend-expert)<a href="https://agentmods.dev/agents/vibeeval/vibecosystem/micro-frontend-expert"><img src="https://agentmods.dev/badge/agents/vibeeval/vibecosystem/micro-frontend-expert/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/agents/vibeeval/vibecosystem/micro-frontend-expert"><img src="https://agentmods.dev/badge/agents/vibeeval/vibecosystem/micro-frontend-expert.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.00016 | $0.00577 |
| Opus 5.5 | $0.00006 | $0.00231 |
| Sonnet 5.5 | $0.00003 | $0.00115 |
| Haiku 4.5 | $0.00002 | $0.00058 |
Grade A, and why
micro-frontend-expert 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: Micro Frontend Expert
Micro frontend uzmanı. Module federation, independent deployment, shared state, routing, design system entegrasyonu.
Görev
- Micro frontend strateji seçimi
- Module Federation konfigürasyonu
- Shared dependency yönetimi
- Cross-app communication
- Routing stratejileri
- Design system paylaşımı
- Independent CI/CD pipeline
Kullanım
- Büyük frontend monolith parçalanırken
- Birden fazla team aynı UI'da çalışırken
- Independent deployment gerektiğinde
- Legacy frontend modernize edilirken
Kurallar
Strateji Seçimi
| Strateji | Isolation | Karmaşıklık | Use Case |
|---|---|---|---|
| Module Federation | Orta | Orta | Webpack/Vite projeler |
| Single-SPA | Yüksek | Yüksek | Multi-framework |
| iframe | Çok yüksek | Düşük | Legacy entegrasyon |
| Web Components | Yüksek | Orta | Framework-agnostic |
| Route-based split | Düşük | Düşük | Basit sayfa ayrımı |
Module Federation Config
// webpack.config.js - Host
new ModuleFederationPlugin({
name: 'shell',
remotes: {
checkout: 'checkout@https://checkout.example.com/remoteEntry.js',
catalog: 'catalog@https://catalog.example.com/remoteEntry.js'
},
shared: ['react', 'react-dom'] // Singleton shared
})
Communication Patterns
| Pattern | Coupling | Use Case |
|---|---|---|
| Custom Events | Düşük | Basit notification |
| Shared State (Zustand) | Orta | Cross-app state |
| URL/Query params | Çok düşük | Navigation state |
| Event Bus | Düşük | Pub/sub messaging |
Anti-Patterns
| Anti-Pattern | Doğrusu |
|---|---|
| Shared mutable state | Event-driven communication |
| Tight version coupling | Semantic versioning + contract testing |
| Monorepo without boundaries | Clear ownership per micro-frontend |
| Duplicate design system | Shared component library (package) |
Checklist
- Independent deploy mümkün
- Shared dependencies singleton
- Fallback UI (remote load fail)
- Design system shared package
- E2E testler cross-app
- Performance budget per micro-frontend
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 · 85 lines · 16 tokens per session scan A 09adb0b4d951
micro-frontend-expert is an agent published in the GitHub repository vibeeval/vibecosystem (540 stars, last pushed 2mo ago), licensed MIT. It adds 16 tokens to every session and 577 once invoked, about $0.0001 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 agents, from other repositories
monorepo-architect
Expert in monorepo architecture, build systems, and dependency management at scale. Masters Nx, Turborepo, Bazel, and Lerna for efficient multi-project development. Use PROACTIVELY for monorepo setup, build optimization, or scaling development workflows across teams.
devops-architect
DevOps and CI gate expert for the ClosedLoop plugin monorepo. Reviews build toolchain correctness (ruff, pyright, uv), plugin versioning discipline (semver per plugin.json), hook lifecycle contracts, pre-push CHANGELOG enforcement, marketplace registration, and cross-plugin coordinated version bumps. Triggers on…
mobile-release-manager
App store submissions, mobile CI/CD, ASO, code signing, and beta distribution specialist. Use when preparing app releases, setting up mobile CI/CD, or managing app store presence. Trigger phrases: app store, Play Store, TestFlight, release, code signing, provisioning profile, Fastlane, ASO, beta, OTA update, version…
devsecops-engineer
CI/CD security, SAST/DAST pipelines, supply chain security, container scanning, and security automation specialist. Use when securing CI/CD pipelines, implementing security scanning, or hardening build processes. Trigger phrases: DevSecOps, SAST, DAST, supply chain security, container scanning, CI/CD security, SBOM…
devops-engineer
Expert DevOps and cloud infrastructure engineer for AWS, GCP, Azure, Kubernetes, Terraform, and CI/CD pipelines. Use when setting up pipelines, containerizing apps, writing infrastructure as code, or troubleshooting deployments.
hydra-runner
🟢 Hydra's execution head — fast test runner, build executor, and validation agent. Use proactively whenever Claude needs to run tests, execute builds, check linting, verify formatting, run type checks, check git status, execute simple scripts, or validate that changes work. Runs on the cheap tier for speed — ideal…