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 hristo2612/jinn --skill migrategit clone --depth 1 https://github.com/hristo2612/jinnWrote 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/hristo2612/jinn/migrate)<a href="https://agentmods.dev/skills/hristo2612/jinn/migrate"><img src="https://agentmods.dev/badge/skills/hristo2612/jinn/migrate.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 61 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00015 | $0.01391 |
| Opus 5 | $0.00008 | $0.00696 |
| Sonnet 5 | $0.00003 | $0.00278 |
| Haiku 4.5 | $0.00002 | $0.00139 |
Grade A, and why
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 yesterday.
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 — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Migrate Skill
Trigger
This skill activates when the user runs /migrate, when launched by jinn migrate, or when asked to update/upgrade the instance.
Overview
When a new version of Jinn is released, it may include updated skills, new documentation, improved prompts, or config schema changes. These updates are shipped as migration folders in ~/.jinn/migrations/<version>/. Each folder contains:
MIGRATION.md- AI-readable instructions describing exactly what changedfiles/- New or updated files in their correct relative directory structure
Your job is to apply these migrations intelligently - preserving user customizations while incorporating improvements.
Steps
1. Read Current Version
Read ~/.jinn/config.yaml and note the jinn.version field. If the field is missing, assume 0.0.0.
2. List Pending Migrations
List all directories in ~/.jinn/migrations/. Each directory name is a semver version string (e.g., 0.2.0, 0.3.0).
Sort them in ascending semver order. Filter to only versions greater than the current instance version.
If no pending migrations exist, inform the user they are up to date and stop.
3. Apply Each Migration In Order
For each pending version, in ascending order:
a. Read the Migration Instructions
Read ~/.jinn/migrations/<version>/MIGRATION.md. This file describes:
- What changed in this version
- Which files are new (safe to copy directly)
- Which files were updated (need intelligent merging)
- Any config schema changes
- Any breaking changes or manual steps
b. Follow the Instructions
The MIGRATION.md will categorize changes:
New files (safe - just copy):
- Copy from
~/.jinn/migrations/<version>/files/<path>to~/.jinn/<path> - These are files that didn't exist before - no conflict possible
Updated files (needs merge):
- The migration provides the new template version of the file
- Read the user's current version of the file
- Compare them and merge intelligently:
- For CLAUDE.md / AGENTS.md: Look for new sections in the template that don't exist in the user's file. Append them. Never remove user customizations.
- For config.yaml: Add new keys with their default values. Never overwrite existing user values.
- For skills: If the user hasn't modified the skill (compare with previous template version if available), replace it. If modified, merge new instructions while preserving customizations.
- For docs: Replace entirely - these are reference docs, not user-customized.
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.
- yesterday Changed · +67 lines · -5 tokens per session a085cf9f696c
- 8d ago First seen · 88 lines · 20 tokens per session scan A 67de0a612bf2
migrate is a skill published in the GitHub repository hristo2612/jinn (315 stars, last pushed yesterday), licensed MIT. It adds 15 tokens to every session and 1,391 once invoked, about $0.0001 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…