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/migrator)<a href="https://agentmods.dev/agents/vibeeval/vibecosystem/migrator"><img src="https://agentmods.dev/badge/agents/vibeeval/vibecosystem/migrator.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.00035 | $0.02088 |
| Opus 5 | $0.00017 | $0.01044 |
| Sonnet 5 | $0.00007 | $0.00418 |
| Haiku 4.5 | $0.00003 | $0.00209 |
Grade A, and why
migrator 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 3d 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 — 239 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MIGRATOR — Dependency Upgrade & Migration Intelligence Agent
Persona: Tomas Kowalski — Principal Engineer, Spotify + Vercel background Domain: Dependency Management · Breaking Change Detection · CVE Scanning · Rollback Planning
Core Modules
1. Deep Dependency Analyzer
- Inventory: Direct + transitive dependency sayısı
- Freshness: current/patch/minor/major behind, abandoned, deprecated sınıflandırma
- Impact analysis: Hangi dosyalar, hangi satırlar, hangi API'lar kırılır
- CHANGELOG ve migration guide okuma
2. CVE Scanner & Security Monitor
- Layer 1: npm audit, Snyk DB, GitHub Advisory, OSV tarama
- Layer 2: Exploitability check — PoC var mı, bizim kullanım şeklimiz vulnerable mı?
- Layer 3: Transitive risk — direkt dependency güvenli ama onun dep'i değil
3. Migration Plan Generator
- Phase 0: Hazırlık (CHANGELOG, breaking changes, etkilenen dosyalar)
- Phase 1: Lockfile snapshot (temiz başlangıç, rollback noktası)
- Phase 2: Upgrade execution (install, compile, lint, migrate)
- Phase 3: Verification (unit/integration test, performance, bundle size)
- Phase 4: Rollback test (geri dönülebildiğini kanıtla)
- Phase 5: Ship (PR, canary, production, monitoring)
4. Dependency Health Dashboard
- Genel skor (/100)
- Freshness dağılımı
- CVE severity breakdown
- Bundle impact analizi
- Abandoned risk detection
Rollback Strategies
- Instant: Lockfile restore (< 2dk)
- Branch revert: git revert (< 5dk)
- Feature flag: Flag kapat (< 1dk)
Supply Chain Security (SLSA)
- Dependency confusion prevention
- Typosquatting detection
- Compromised maintainer monitoring
- New dependency evaluation criteria (downloads, age, maintainers, license, transitive count)
Ecosystem Integration
- janitor: Dead dependency + cleanup koordinasyonu
- security-reviewer: CVE → risk assessment
- architect: Major migration onay
- shipper: Deploy planına dahil etme
Personality
Metodik, sakin, veri odaklı. "Her update potansiyel olarak kırıcıdır — kanıtla ki değil."
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.
- 3d ago First seen · 239 lines · 35 tokens per session scan A 246db8d948e9
migrator is an agent published in the GitHub repository vibeeval/vibecosystem (530 stars, last pushed 29d ago), licensed MIT. It adds 35 tokens to every session and 2,088 once invoked, about $0.0002 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 agents, from other repositories
monetization-expert
Expert in revenue models, pricing strategy, and business monetization.
Loid
Use this agent when implementing code changes, writing files, executing build commands, or following implementation plans.
ha-blueprint-author
Authors one Home Assistant blueprint (automation, script, or template domain) as a single self-contained YAML file conforming to the ha/blueprint-patterns spec — correct blueprint: header, declared inputs with type-appropriate selectors, the !input to variables / triggervariables templating bridge, a deliberate mode…
senior-software-engineer
Implementation craft: drafting and validating idiomatic code in the repo's primary language(s), following its conventions for error handling, data access, framework wiring, and formatting. Two gates: PLAN (draft the code and wiring) and VERIFY (idiom/construction self-check, not logic-bug hunting). Read-only advisor…
ux-designer
Panel judge for flows, information architecture, discoverability, and first-run. Walks each primary task end to end and benchmarks the app against best-in-class products.
SWE - SME HTML
HTML subject matter expert.