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 encoredev/skills --skill migrategit clone --depth 1 https://github.com/encoredev/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/skills/encoredev/skills/migrate)<a href="https://agentmods.dev/skills/encoredev/skills/migrate"><img src="https://agentmods.dev/badge/skills/encoredev/skills/migrate/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/encoredev/skills/migrate"><img src="https://agentmods.dev/badge/skills/encoredev/skills/migrate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00045 | $0.05829 |
| Opus 5.5 | $0.00018 | $0.02332 |
| Sonnet 5.5 | $0.00009 | $0.01166 |
| Haiku 4.5 | $0.00005 | $0.00583 |
Grade A, and why
encore-migrate 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 20d 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 — 460 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Migrate to Encore
This skill guides migrating any existing backend application to Encore, one migration unit at a time. It supports any source language or framework and targets both Encore.ts and Encore Go. A migration-plan.md summary file and migration-plan/ directory of per-unit detail files are created at the Encore project root to track progress across sessions. This skill contains no Encore code examples — it delegates all Encore-specific implementation to the appropriate language-specific skills.
Phase Detection
Before doing anything, determine which phase to enter:
- No
migration-plan.mdexists in the Encore project directory → Start at Phase 1: DISCOVER migration-plan.mdexists but nomigration-plan/directory → Resume at Phase 2: PLAN (discovery done, detail files not yet written)migration-plan/directory exists with pending units (any unit in the summary with statuspendingorin progress) → Resume at Phase 3: MIGRATE- All units in the summary are
migrated,skipped, ormanual validation needed→ Go to Phase 4: COMPLETE
Autonomous Mode
The confirmation stops in this workflow (confirming units in Phase 1, approving the first unit in Phase 2, picking each next unit in Phase 3) are the default. If the user asks to run the migration through without stopping ("just migrate it", "do them all", "don't ask"), skip those stops:
- Pick sensible defaults for open decisions (see "Key Decisions" in Phase 1) and state each one to the user in a short list before writing code
- Record every default in the
## Decisionssection ofmigration-plan.mdso it can be revisited - Still ask before side-effecting HTTP calls against the source system, and never modify the source
- Still validate every entity before marking it
migrated
Resuming a Migration (Phase 3)
When migration-plan.md and migration-plan/ exist with pending units:
- Read
migration-plan.md(summary only — do NOT read all detail files) - Report current status to the user — for example: "3 of 7 units migrated, next suggested: billing (all its dependencies are migrated)"
- Ask the user what they would like to work on next, offering a suggestion based on the dependency order in the plan
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.
- 20d ago Changed · +37 lines 993c08b21ec2
- 2mo ago First seen · 423 lines · 45 tokens per session scan A 8d617d1e00fd
encore-migrate is a skill published in the GitHub repository encoredev/skills (30 stars, last pushed 4d ago), licensed Apache-2.0. It adds 45 tokens to every session and 5,829 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-08-30.
Other skills, from other repositories
build-mcp-server
This skill should be used when the user asks to "build an MCP server", "create an MCP", "make an MCP integration", "wrap an API for Claude", "expose tools to Claude", "make an MCP app", or discusses building something with the Model Context Protocol. It is the entry point for MCP server development — it interrogates…
data-manager-api-setup
Guides developers through client library installation and authentication setup steps for the Data Manager API. Use this skill when a user is getting started with the Data Manager API and needs to setup their local environment, install the client library, or setup access to the API. Don't use for implementing audience…
vss-manage-video-io-storage
Use to drive vss vios for sensor list, timelines, clips, snapshots, and add/delete of video or stream sources, and the VIOS REST API only for what that CLI does not cover (sensor info/status/settings, storage and recorder status, WebRTC, the RTSP proxy, network scan, device settings, bytes to disk, the NvStreamer…
workers-best-practices
Cloudflare Workers best practices for production applications. Use when writing, reviewing, or configuring Workers.
vss-search-archive
Use this skill when a user wants to search archived VSS video that is already registered in a configured deployment — by natural-language, similarity, attribute, object-ID, or lexical tag query. Not for fresh clip Q&A, live captioning, video summarization, deployment, or source ingestion/deletion.
new
Create a new project to start development quickly.