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 yangyifan18/dotvibe --skill dotvibe-migrationgit clone --depth 1 https://github.com/yangyifan18/dotvibeWrote 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/yangyifan18/dotvibe/dotvibe-migration)<a href="https://agentmods.dev/skills/yangyifan18/dotvibe/dotvibe-migration"><img src="https://agentmods.dev/badge/skills/yangyifan18/dotvibe/dotvibe-migration/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/yangyifan18/dotvibe/dotvibe-migration"><img src="https://agentmods.dev/badge/skills/yangyifan18/dotvibe/dotvibe-migration.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.00101 | $0.00833 |
| Opus 5 | $0.00051 | $0.00417 |
| Sonnet 5 | $0.00020 | $0.00167 |
| Haiku 4.5 | $0.00010 | $0.00083 |
Grade A, and why
dotvibe-migration 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 9d 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 — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dotvibe Migration
Guide users through dotvibe migrations as a choice-driven assistant. The user should be able to use simple natural language such as 调用 dotvibe 导出记忆 or 调用 dotvibe 导入旧 Mac 的记忆，备份在 <path>; do not require them to name this skill or provide dotvibe commands.
Start Here
- Read
references/intents.mdand classify the user's natural-language intent. - Run
dotvibe agent doctor --jsonbefore any export/import/setup/write workflow. - For source Mac export, read
references/source-export.md. - For destination Mac import, read
references/destination-import.md. - If
import-planreportsproject_relocations, or the user mentions a changed username/home path, missing project checkout, clone, repo mismatch, or loading old project memory, readreferences/project-relocation.md. - If project memory conflicts exist, a stage directory exists, or the user asks to review/merge memory, read
references/memory-merge.md. - For risky actions, recipe apply, installer commands, overwrites, or lint overrides, read
references/safety.md. - For validating the skill behavior itself, read
references/testing.md.
Natural Language Entrypoints
These prompts should trigger the standard flow without asking the user to restate commands:
调用 dotvibe 导出记忆调用 dotvibe 导入旧 Mac 的记忆，备份在 ~/Downloads/dotvibe.tar.gz帮我备份这台 Mac 上的 Claude Code / Codex / OpenCode 记忆帮我把旧 Mac 的 AI coding 记忆恢复到这台新 Mac帮我导出一个可以分享给团队的 vibe recipe帮我应用这个 .vibe recipe新 Mac 用户名变了，帮我加载旧项目 memory
Rules
- Ask choice-style questions; avoid open-ended command prompts.
- Do not ask users to choose raw flags when the skill can translate choices into dotvibe commands.
- Always run a JSON plan or dry-run before writing.
- Before direct full-archive imports or
--force, require either a fresh destination-side backup or a staging workspace the user has reviewed. - Never use
--force,--yes, setup installs,git clone, recipe apply, or direct import writes without explicit user confirmation. - Prefer
dotvibe import --stagefor existing project memory. - If per-project relocation safety conflicts with a top-level
safe-to-importrecommendation, choose the safer per-project path. - Do not paste secrets or full private memory into chat unless the user explicitly asks after a warning.
- After any write, summarize the result and show recovery instructions. Recipe apply creates rollback records; full archive import currently requires the pre-import backup, staged local copies, or manual recovery.
What ships with it
8 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.
- 9d ago First seen · 50 lines · 101 tokens per session scan A c1a4f5c64ea8
dotvibe-migration is a skill published in the GitHub repository yangyifan18/dotvibe (5 stars, last pushed 3mo ago), licensed MIT. It adds 101 tokens to every session and 833 once invoked, about $0.0005 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-08-31.
Other skills, from other repositories
handover
Use when wrapping up or capturing the current state of a coding session — writes a short, dated entry to the repo's RepoHandover.md so a future agent or you can resume without grepping archived sessions. Triggers on "handover", "hand off", "write handover", "capture state", "checkpoint this session".
engraphis-memory
Give the agent durable, scoped, explainable memory across sessions and repositories through the Engraphis MCP tools. Use when you learn a convention, decision, bug cause/fix, or user preference worth keeping; when prior context would help before you answer or act (to avoid re-asking or re-deriving); when asked "why is…
marm-init
Guided MARM MCP setup. Invoke after running marm-memory init on the CLI to configure MARM memory across your agent. Drives transport choice, runtime choice, MCP config writing, multi-agent linking, and server start. Works on Claude, Codex, Gemini, Qwen, Cursor, VS Code, and other MCP-capable agents.
init
Turn on Rekal memory in the current repository by running rekal init. Use when the user asks to initialize or set up Rekal here, or when a rekal command reported the repository is not initialized. Once per repository. Do not offer this merely because a repo lacks a .rekal/ store — most repos do not want one.
install
Install the Rekal binary on this machine. Use when rekal is not on PATH — a command reported command not found — or when the user asks to install Rekal. Once per machine, not per repository; to set up a repo that already has the binary, use the init skill instead.
boss-briefing
Vault health check — workflow pattern analysis, profile sync, session gap recovery, persona rule proposals.