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 agentmods add commands/zhyx12/projtool/migrate-docsgit clone --depth 1 https://github.com/zhyx12/projtoolWhat 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.00043 | $0.00709 |
| Opus 5 | $0.00022 | $0.00354 |
| Sonnet 5 | $0.00009 | $0.00142 |
| Haiku 4.5 | $0.00004 | $0.00071 |
Grade A, and why
migrate-docs 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/migrate-docs — adopt an old docs layout into the registry
This project's docs may predate the registry: standing plans under plans/
and experiment scratch under exp/. This command adopts them into
docs/registry/ so lineage tooling (thread_tree, edges, freezes) works. The
tool never guesses history — the human confirms every decision.
Steps
-
Scan.
mcp__projtool__reconcile_docs(read-only, never raises) reports drift as findings. Present them grouped by kind, one line each:unregistered_experiment_dir,unregistered_thread_dir,unregistered_plan,invalid_record,broken_doc_ref,graph_violation,runs_index_corrupt. If it comes back clean and there are noplans/orexp/directories, the project is already migrated (or has nothing to adopt) — say so and stop. -
Dry-run.
mcp__projtool__migrate_docs_layout()(no args) returns a proposal. Show it as a table:threads_to_create— proposed threads, each with its sourcefrom_plan;experiments— each withsuggested_thread,suggestion_reason,runs_found, andsuggested_status;already_registered— what's left alone. The dry-run always works — dirty plan files are checked at apply time, not here.
-
Confirm the mapping WITH THE USER. The
suggested_*fields are suggestions, not decisions. Build amappingthat decides every proposed experiment — the tool refuses a partial mapping. For each<exp_slug>, the value is{"thread": <existing/proposed thread slug | thr_ id | "_scratch" | "skip">}with an optional"status"override (planned|running|finalized|abandoned)."_scratch"routes it under the built-in scratch thread;"skip"leaves it unadopted (and still counts as a decision). Walk the user through it; do not fill it in yourself. -
Apply.
mcp__projtool__migrate_docs_layout(apply=True, mapping={...}). If it refuses because plan files have uncommitted changes, it names them — commit those first (narrowgit add) and re-apply. Report the summary: created threads, imported experiments (stampedimported, with no edges and an empty frozen block — the tool never reconstructs history), runs backfilled, and plan files git-mv'd intothreads/<slug>/plan.md. Then runreconcile_docsagain and show it comes back clean (or exactly what remains).
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 First seen · 51 lines · 43 tokens per session scan A 86e97895c6d9
migrate-docs is a command published in the GitHub repository zhyx12/projtool (1 stars, last pushed 18d ago), licensed MIT. It adds 43 tokens to every session and 709 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.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.