A command for bringing Spec Harness into an existing codebase. It first indexes source files and exported symbols, then creates the harness's memory bank, rules, agents, and workflow while preserving the existing entry point.

It helps document source roots, files, and exported code, then add Spec Harness to the project. It is used when adopting the harness in a codebase that already exists.

It gives coding agents a structured map of an established project before they work on it. This avoids treating an existing codebase like a new, empty project.

migrate — Command for Claude Code by chohra-med

Install

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.

Clone the repo

git clone --depth 1 https://github.com/chohra-med/expo_boilerplate

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/chohra-med/expo_boilerplate/migrate/github.svg)](https://agentmods.dev/commands/chohra-med/expo_boilerplate/migrate)

Your own site

<a href="https://agentmods.dev/commands/chohra-med/expo_boilerplate/migrate"><img src="https://agentmods.dev/badge/commands/chohra-med/expo_boilerplate/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/chohra-med/expo_boilerplate/migrate"><img src="https://agentmods.dev/badge/commands/chohra-med/expo_boilerplate/migrate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 537 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.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.00537
Opus 5	$0.00000	$0.00269
Sonnet 5	$0.00000	$0.00107
Haiku 4.5	$0.00000	$0.00054

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

Security

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

.claude/commands/spec-harness/migrate.md · 39 lines

How it starts

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

Command: `migrate` — adopt Spec Harness into an EXISTING codebase

Same as init, but the code already exists. The order flips: index first, so the memory bank and rules describe what's really there, not a blank template. This is capability 3, "if the project already exists, index it into a memory bank."

Invocation

spec-harness index <target>          # 1. build the structural index (fast, scripted)
spec-harness init <target> <name>    # 2. lay down bank + rules + agents (preserve any existing entry point)
# 3. run the sdd-researcher to enrich the index + fill the bank from real code (agent step)

Steps

Index (scripted). bin/sh-index.sh walks the source roots (src/ app/ lib/ packages/ service/ ...), inventories every source file with its exported symbols, and writes ai_rules/context_map.md + per-root README.inventory.md. This is the skeleton the agents navigate by instead of grepping.
Scaffold (scripted). sh-init.sh lays down the bank, rules, agents, loop. If a CLAUDE.md / AGENTS.md / .cursorrules already exists, merge — append the Spec Harness startup block, preserve the project's rules under a ## Pre-existing project rules heading. Never overwrite blind.
Enrich (agent). Run the sdd-researcher to turn the raw inventory into real understanding: what each module does, which symbols are reusable, the patterns already in use. It fills .memory/00/10/20/30 from the actual code, and writes stack-correct frequent_rules.md from the conventions it observes plus researched best practices. Fill, don't leave [TBD].
Verify. Diff the inventory file count against the source dirs (the audit command does this as "index drift"). Confirm the bank references real symbols. Confirm frequent_rules.md is stack-correct, not copied from another project.

Rule

Skipping the index step on an existing codebase is refused. The index is the layer that prevents hallucination and makes reuse automatic. Without it you have a decorative bank, which is the exact failure mode of every SDD tool that hand-writes its standards.

Read the full file on GitHub · 39 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.

9d ago First seen · 39 lines · 0 tokens per session scan A c031f072940a

Subscribe to this mod's changes

migrate is a command published in the GitHub repository chohra-med/expo_boilerplate (32 stars, last pushed 7d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 537 tokens. 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.

Planning ai boilerplate cursor expo react-native

arc-skill

You are scaffolding a new React Native (Expo) project using the arc-skill architecture.

art9mid/arc-skill · 0 tokens

arc-connect

Connect API layer, storage, state management, authentication, and i18n to an existing React Native Expo project. Use after arc-scaffold to add backend integration. Trigger when the user mentions adding API calls, auth flow, login, storage, state management, internationalization, backend connection, or data fetching to…

art9mid/arc-skill · 70 tokens

arc-scaffold

Scaffold a new React Native Expo project with folder structure, dependencies, TypeScript config, linting, and navigation shell. Use when starting a new mobile app from scratch, when the user says 'create a new app', 'start a project', 'set up React Native', 'init Expo app', or needs project boilerplate. Trigger this…

art9mid/arc-skill · 83 tokens

arc-ui

Add theme system, reusable components, screen layouts, and mobile UX design to a React Native Expo project. Use after arc-scaffold to build the visual layer. Trigger when the user wants to add a theme, dark mode, UI components, buttons, inputs, screen layouts, design system, or visual polish to their React Native app.

art9mid/arc-skill · 70 tokens

arc-audit

Audit a React Native Expo project for mobile UX issues, performance problems, and architecture violations. Use to check code quality against arc-skill best practices. Trigger when the user asks to review code, check for issues, wants a health check, mentions touch targets, accessibility, performance audit, or says 'is…

art9mid/arc-skill · 76 tokens

arc-feature

Add a complete new feature domain to an existing React Native Expo project — types, API module, React Query hooks, screen, and components in one go. Use when adding a new entity like products, orders, chat, users, recipes, or any CRUD resource. Trigger when the user says 'add a feature', 'create a new screen for X'…

art9mid/arc-skill · 94 tokens