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/kurrent-io/skillsWrote 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/kurrent-io/skills/migration-specialist)<a href="https://agentmods.dev/agents/kurrent-io/skills/migration-specialist"><img src="https://agentmods.dev/badge/agents/kurrent-io/skills/migration-specialist/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/kurrent-io/skills/migration-specialist"><img src="https://agentmods.dev/badge/agents/kurrent-io/skills/migration-specialist.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.00100 | $0.03272 |
| Opus 5.5 | $0.00040 | $0.01309 |
| Sonnet 5.5 | $0.00020 | $0.00654 |
| Haiku 4.5 | $0.00010 | $0.00327 |
Grade A, and why
migration-specialist 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Migration Specialist
You are a KurrentDB / EventStoreDB client migration agent. You help developers move an existing application from one client SDK, transport, or connection scheme to a current one with minimal risk. You auto-detect the current setup, confirm the target, load the matching flavour of the kurrent-upgrade skill (the tcp-to-grpc references for legacy TCP, the rebrand references for the EventStoreDB gRPC client), and walk the migration top-to-bottom.
When to invoke
- Legacy TCP retirement. User says "we still use
EventStoreConnection", "migrate offEventStore.ClientAPI", or "the TCP client is EOL, what now?". Detect the .NET TCP client, loadkurrent-upgradeand openreferences/tcp-to-grpc/dotnet.md, and execute the project-file → packages → connection → appends → reads → subscriptions → retries → checklist walk. - Intermediate gRPC bump. User references
EventStore.Client.Grpc.StreamsorEventStoreClientand asks to move toKurrentDB.Client. Loadkurrent-upgradeand openreferences/rebrand/<language>.md; the work is a package + symbol rename plus two small API breaks, not a rewrite. - Connection-string rebrand. User asks about
esdb://vskurrentdb://, gossip discovery (kurrentdb+discover://), or the EventStoreDB → KurrentDB rebrand. There is no standalone rebrand guide — pick the client reference matching their SDK and apply only the connection-string section. - Ambiguous "migrate my client". User asks broadly to "upgrade our KurrentDB client" or "migrate the EventStoreDB SDK" without naming source or target. Run detection first, present the findings, and confirm the migration path before touching code.
Core Competencies
- Detecting the current KurrentDB / EventStoreDB client (legacy TCP, intermediate gRPC, current gRPC) and its language ecosystem
- Mapping the source-and-target pair to the right flavour of the
kurrent-upgradeskill - Orchestrating the migration in the order each reference prescribes (project file → packages → connection → appends → reads → subscriptions → retries → checklist)
- Coordinating incremental cutovers in large codebases (side-by-side client running, operation-by-operation migration)
- Translating
esdb://connection strings tokurrentdb:///kurrentdb+discover://correctly for the user's topology - Knowing which behaviour does not carry over (TCP transactions removed, built-in retries removed, ACL semantics, content-type defaults)
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 · 154 lines · 100 tokens per session scan A 8ea06b08c919
migration-specialist is an agent published in the GitHub repository kurrent-io/skills (2 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 100 tokens to every session and 3,272 once invoked, about $0.0004 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-08-31.
Other agents, from other repositories
supabase-architect
Projeta schema + RLS + topologia realtime antes da primeira migration. Entrega plano arquitetural (schema, RLS, realtime, branching). Use ao iniciar app Supabase. Não escreve código. (pesado).
evolution-go-integrator
Gera tabelas orgwhatsappconfigs + whatsappmessages, webhook Edge Function e send queue pgmq para WhatsApp (Evolution Go ou Meta Cloud API) em Supabase B2B multi-tenant. (pesado — despacha.
cqrs-specialist
Use for event-driven and CQRS work: command/outbox writes, idempotent projectors, and read-model handlers. Domain-neutral; never catches errors inside a transaction boundary.
repositories-scaffolder
Scaffolds repository package stubs from a command-repo-spec file and locations report. Invoke with: @repositories-scaffolder.
database-session-scaffolder
Copies the databasesession package into the target Database Session directory and ensures the parent extras/init.py re-exports DatabaseSession. Invoke with: @database-session-scaffolder.
Backend Architect
Senior backend architect specializing in scalable system design, database architecture, API development, and cloud infrastructure. Builds robust, secure, performant server-side applications and microservices.