migrate-to-guidance

migrate-to-guidance is a skill for Claude Code from juicesharp/rpiv-mono. It costs 93 tokens per session (1,135 once invoked), scanned A, original, MIT.

A migration tool for moving project instructions from CLAUDE.md files into a central .rpiv/guidance/ folder. CLAUDE.md files are instruction files placed inside a project for an AI coding assistant.

In plain words
What is it for?
Use it to find all CLAUDE.md files, preview where they will move, and create matching architecture.md files in the guidance folder. It can optionally remove the original files.
Why use it?
It avoids having the same kind of guidance scattered throughout the codebase. It also updates references so the moved instructions continue to point to the right places.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions CLAUDE.md.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is node scripts/migrate.js --project-dir "${CWD}" --dry-run.

Good fit Use it to find all CLAUDE.md files, preview where they will move, and create matching architecture.md files in the guidance folder. It can optionally remove the original files.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/juicesharp/rpiv-mono
agentmods
npx agentmods add skills/juicesharp/rpiv-mono/migrate-to-guidance

Made for: Claude Code.

Wrote 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.

agentmods badge for migrate-to-guidance

README.md
[![agentmods](https://agentmods.dev/badge/skills/juicesharp/rpiv-mono/migrate-to-guidance/github.svg)](https://agentmods.dev/skills/juicesharp/rpiv-mono/migrate-to-guidance)
Your own site
<a href="https://agentmods.dev/skills/juicesharp/rpiv-mono/migrate-to-guidance"><img src="https://agentmods.dev/badge/skills/juicesharp/rpiv-mono/migrate-to-guidance/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.

agentmods 80×15 button for migrate-to-guidance

Your own site · 80×15
<a href="https://agentmods.dev/skills/juicesharp/rpiv-mono/migrate-to-guidance"><img src="https://agentmods.dev/badge/skills/juicesharp/rpiv-mono/migrate-to-guidance.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 93 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,135 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00093 $0.01135
Opus 5 $0.00046 $0.00567
Sonnet 5 $0.00019 $0.00227
Haiku 4.5 $0.00009 $0.00113

Measured 13d ago against content hash 4f83f55b40ff, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

migrate-to-guidance 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 13d 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.

packages/rpiv-pi/skills/migrate-to-guidance/SKILL.md · 111 lines

How it starts

The opening of the file, as written. The whole thing — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Migrate CLAUDE.md to Guidance

You are tasked with migrating a project's existing CLAUDE.md files (typically created by /skill:annotate-inline) into the .rpiv/guidance/ system.

The migration relocates files from in-place CLAUDE.md to .rpiv/guidance/{path}/architecture.md and transforms internal cross-references.

Input

$ARGUMENTS — optional --delete-originals flag to remove the source CLAUDE.md files after migration.

Steps to follow:

  1. Pre-flight check:

    • Use Glob to find all **/CLAUDE.md files in the project
    • If none are found, inform the user: "No CLAUDE.md files found in this project. Nothing to migrate." and stop
    • If .rpiv/guidance/ already exists, note this — there may be conflicts
  2. Dry run — preview the migration:

    • Run the migration script in dry-run mode:
      node scripts/migrate.js --project-dir "${CWD}" --dry-run
      
    • Parse the JSON output from stdout and present a migration plan to the user:
      ## Migration Plan
      
      Found {N} CLAUDE.md files to migrate:
      
      | Source | Target | Lines |
      |--------|--------|-------|
      | CLAUDE.md | .rpiv/guidance/architecture.md | 45 |
      | src/core/CLAUDE.md | .rpiv/guidance/src/core/architecture.md | 78 |
      | ... | ... | ... |
      
    • If there are conflicts (targets that already exist), list them:
      ### Conflicts (targets already exist):
      - .rpiv/guidance/src/core/architecture.md
      
      Use --force to overwrite these.
      
    • If there are warnings (unresolved prose references), list them:
      ### Warnings:
      - .rpiv/guidance/architecture.md line 23: Prose reference may need manual update
      
    • Ask the user for confirmation before proceeding. Ask whether they want to:
      • Delete the original CLAUDE.md files after migration (--delete-originals)
      • Overwrite existing conflicts (--force)
  3. Execute the migration:

    • Build the command based on user choices:
      node scripts/migrate.js --project-dir "${CWD}" [--delete-originals] [--force]
      
    • Run the migration and parse the JSON output
    • Present the results:
      ## Migration Complete
      
      | Source | Target | Lines | Refs Updated |
      |--------|--------|-------|--------------|
      | CLAUDE.md | .rpiv/guidance/architecture.md | 45 | 3 |
      | src/core/CLAUDE.md | .rpiv/guidance/src/core/architecture.md | 78 | 1 |
      | ... | ... | ... | ... |
      
      Total: {N} files migrated
      {Originals deleted: yes/no}
      

Read the full file on GitHub · 111 lines

Changes

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.

  1. 13d ago First seen · 111 lines · 93 tokens per session scan A 4f83f55b40ff

Subscribe to this mod's changes

migrate-to-guidance is a skill published in the GitHub repository juicesharp/rpiv-mono (780 stars, last pushed yesterday), licensed MIT. It adds 93 tokens to every session and 1,135 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-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens