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.
git clone --depth 1 https://github.com/Desko77/cursor-1c-skillsWrote 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/commands/desko77/cursor-1c-skills/move-project)<a href="https://agentmods.dev/commands/desko77/cursor-1c-skills/move-project"><img src="https://agentmods.dev/badge/commands/desko77/cursor-1c-skills/move-project.svg" alt="Measured on agentmods" height="20"></a>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.00779 |
| Opus 5 | $0.00000 | $0.00390 |
| Sonnet 5 | $0.00000 | $0.00156 |
| Haiku 4.5 | $0.00000 | $0.00078 |
Grade A, and why
move-project 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 7d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- move-project — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Перенеси проект в другую папку, сохранив память, сессии и планы Claude Code.
Аргумент $ARGUMENTS
Пользователь передает:
- Путь к проекту-источнику (откуда)
- Путь назначения (куда)
- Или пустую строку - тогда спроси оба пути
Пример: /move-project C:\Projects\my-app D:\Work\my-app
Выполнение
1. Подготовка
Проверь что источник существует, назначение свободно. Если назначение уже существует - спроси пользователя.
2. Перемещение файлов проекта
mv "<source>" "<target>"
Если mv не работает (Device or resource busy) - скопируй через PowerShell:
powershell -Command "Copy-Item -Path '<source>' -Destination '<target>' -Recurse -Force"
Потом попроси пользователя закрыть все что держит папку и удали оригинал.
3. Определение папки памяти Claude Code
ВАЖНО: Claude Code нормализует путь проекта в имя папки ~/.claude/projects/:
- Разделители (
\,/,:) → дефис- - Подчеркивание (
_) → дефис (-)
Пример: C:\My Projects\Sub_folder\my-app → C--My-Projects-Sub-folder-my-app
Алгоритм:
- Открой Claude Code в новом расположении (или попроси пользователя открыть)
- Посмотри какую папку Claude Code реально создал:
ls ~/.claude/projects/ | grep <имя-проекта> - Используй ту папку, которую создал Claude Code - НЕ конструируй имя вручную
4. Перенос памяти
Из всех старых папок проекта в ~/.claude/projects/ (может быть несколько вариантов):
OLD="~/.claude/projects/<old-project-folder>"
NEW="~/.claude/projects/<new-project-folder>"
# Память
cp "$OLD/memory/"* "$NEW/memory/"
# Сессии (.jsonl файлы)
cp "$OLD/"*.jsonl "$NEW/"
# Папки сессий (UUID-папки)
for d in "$OLD/"*/; do
dirname=$(basename "$d")
[ "$dirname" != "memory" ] && cp -r "$d" "$NEW/$dirname"
done
5. Планы
Планы хранятся в ~/.claude/plans/<имя-проекта>/ где имя = последний каталог пути. Если имя каталога проекта не изменилось - планы остаются на месте, ничего делать не нужно.
Если имя изменилось:
mv ~/.claude/plans/<old-name> ~/.claude/plans/<new-name>
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.
- 7d ago First seen · 91 lines · 0 tokens per session scan A c064dcdaafab
move-project is a command published in the GitHub repository Desko77/cursor-1c-skills (55 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 779 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.
Other commands, from other repositories
move-project
A command for moving a project to another folder while keeping Claude Code's saved memory, sessions, and plans.
docx-to-md
A local command that converts a Microsoft Word DOCX document into a Markdown text file, also extracting its images into an adjacent folder.
check-uuid
A checker for duplicate UUIDs in 1C MDO metadata files. UUIDs are identifiers that should be unique within the relevant files.
browser-debug
A command for starting Yandex Browser with remote debugging enabled. Remote debugging lets developer tools connect to a running browser through the Chrome DevTools Protocol, a standard interface for inspecting web pages.
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.