A migration command that moves Markdown files from scattered project folders into docs-cockpit's standard documentation layout. Markdown is a plain-text format commonly used for project documents.

Importing plans, tasks, architecture documents, decisions, project guides, and other Markdown files into dashboard categories with generated IDs, metadata, and configuration.

Older projects may store plans, decisions, specifications, and guides in different folders, which can leave the dashboard empty or incomplete. This organizes them and adds the metadata docs-cockpit needs.

migrate — Command for coding agents by Guohao1020: A migration command that moves Markdown files from scattered…

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.

agentmods

npx agentmods add commands/guohao1020/docs-cockpit/migrate

Clone the repo

git clone --depth 1 https://github.com/Guohao1020/docs-cockpit

Or install docs-cockpit, the plugin that ships this one along with the rest of its 3 skills, 5 commands, 1 hook.

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/guohao1020/docs-cockpit/migrate.svg)](https://agentmods.dev/commands/guohao1020/docs-cockpit/migrate)

Your own site

<a href="https://agentmods.dev/commands/guohao1020/docs-cockpit/migrate"><img src="https://agentmods.dev/badge/commands/guohao1020/docs-cockpit/migrate.svg" alt="Measured on agentmods" height="20"></a>

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

When invoked 1,169 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

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	$0.00040	$0.01169
Opus 5	$0.00020	$0.00584
Sonnet 5	$0.00008	$0.00234
Haiku 4.5	$0.00004	$0.00117

Measured 4d ago against content hash 0b6ae8a8b487, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 4d 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.

commands/migrate.md · 63 lines

How it starts

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

Explicit invocation of docs-cockpit migrate — for projects that don't already have docs/spec/module/*.md with frontmatter. Use this on legacy / bastion-style repos with scattered docs/plans/, docs/adrs/, docs/PRD/, etc.

When to use

User says: "迁移这个项目到 docs-cockpit / 帮我用 docs-cockpit 跑起来 / set up dashboard for this legacy project"
docs-cockpit render reports [WARN] 0 items because the project layout doesn't match defaults
The docs-cockpit-build skill's bootstrap workflow detects a non-canonical layout (e.g. docs/plans/ + docs/adrs/ instead of docs/spec/module/)

What it does

Scans the project for MDs in known dirs:
- docs/spec/module/, docs/plans/, docs/tasks/, docs/adrs/, docs/superpowers/{plans,specs}/ → modules
- docs/spec/concept/, docs/concepts/ → concepts
- Root: README / CLAUDE.md / AGENTS.md / GEMINI.md / PROGRESS.md / CHANGELOG.md / PRE-LAUNCH-CHECKLIST.md / dogfood-onboarding.md / DESIGN.md → system_docs (each as own entry)
- Dirs: docs/PRD/, docs/RFC/, docs/architecture/, docs/DESIGN/, docs/audits/, docs/review/ → system_docs (each as whole-dir entry)
Assigns IDs (M01, M02, ... for modules; C01, ... for concepts)
Generates frontmatter for each module/concept:
- id (new), title (from H1 or filename), status: not-started, sprint: M0, progress: 0 as defaults
- Existing frontmatter fields are preserved (don't override user's status/progress if already set)
Physically moves files to docs/spec/module/M{NN}-{slug}.md / docs/spec/concept/C{NN}-{slug}.md
- Uses git mv to preserve git history (falls back to plain rename if not in git)
- --keep-originals to copy instead of move (preserves docs/plans/ etc.)
Writes docs-cockpit.yaml with project + paths + system_docs + modules/concepts + frontmatter blocks

Steps when user invokes /docs-cockpit:migrate

Always start with dry-run. Run docs-cockpit migrate (no --apply flag) and show the user the plan output. Highlight:
- Number of modules / concepts / system_docs detected
- First 5-10 module file moves so they see the rename pattern
- Whether docs-cockpit.yaml will be overwritten
Wait for explicit user confirmation. Don't auto-apply. The migration physically moves files.
On confirmation, run with --apply (or --apply --keep-originals if user prefers to keep originals).
After apply succeeds, run docs-cockpit render automatically to verify the dashboard generates correctly.
Report: counts of files moved + dashboard render status + any warnings.

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

4d ago First seen · 63 lines · 40 tokens per session scan A 0b6ae8a8b487

Subscribe to this mod's changes

migrate is a command published in the GitHub repository Guohao1020/docs-cockpit (2 stars, last pushed 2mo ago), licensed MIT. It adds 40 tokens to every session and 1,169 once invoked, about $0.0002 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.

Documents Writing and docs claude-code claude-code-plugin claude-skills dashboard frontmatter kanban

nyann:route-docs

Change documentation storage routing (local, Obsidian, Notion, or per-type split) and regenerate the doc scaffold to match.

thettwe/nyann · 34 tokens

pause

Park this session's beacon — enter pause mode, with an optional note.

chris-peterson/beacon · 14 tokens

install-beacon

Bootstrap or refresh beacon's wrapper, completions, status line, and iTerm2 profiles.

chris-peterson/beacon · 18 tokens

deploy

Scaffold/compile/deploy a report to JasperReports Server and verify it renders.

robertgorsuch/AI-JasperReports-Generator · 16 tokens

export-latex

Export the current paper draft to production-ready LaTeX (.tex) and PDF using the arxiv-style template. Converts draft.md + references.bib + figures/ into a complete LaTeX project with resolved citations, tables, and figures. Compiles to PDF automatically.

TobiasBlask/open-paper-machine · 55 tokens

export

Export the case study — PDF if a browser is installed, HTML either way.

vldesigns/casebook · 15 tokens