# Safety Brief Before an Agent Sorts Your Images

> A reusable prompt that turns your folder, rename and undo answers into a one-page brief an image-sorting helper must follow.

## Install

Copy the content below into your project:

# Safety Brief Before an Agent Sorts Your Images

A reusable prompt that turns your folder, rename and undo answers into a one-page brief an image-sorting helper must follow.

## Start here

**What to paste:** copy the complete prompt below into an ordinary AI chat that accepts text. Before that, paste your own answers to the eight questions it asks. If you leave any answer out, the prompt tells the assistant to insert `[NEEDS MY INPUT]` instead of guessing.

**Where to paste it:** any text chat with an AI assistant. No terminal, account setup or file upload is required.

**How to check the output:** the reply should be Markdown with ten numbered headings, fit on roughly one page, and end with a three-line "Before I approve" checklist. Compare it against your own answers:

| Check | Should be true |
|---|---|
| Scope | names one root folder you approved |
| Off-limits list | contains the folders you listed as untouchable |
| Rename example | uses only separators you actually supplied |
| Deletion | shows NO unless you explicitly allowed it |
| Undo plan | understandable without the helper present |

The brief is preparation only. It schedules nothing, reads no files and sends no messages.

## What this is for

Sorting photos is exactly the kind of chore worth handing to a helper, and exactly the kind where guessing goes wrong. This prompt makes you answer eight short questions first — root folder, off-limits folders, current and target naming, destination folders, unmatched files, deletion, and how you want to undo — then turns them into a brief the helper must follow.

## Missing inputs and privacy

If two of your answers contradict each other, the prompt asks which one wins rather than choosing for you. If you never state what happens to unmatched files, it defaults to "leave in place and list them" and labels that as a default you can change.

Treat folder paths as private. Only put into the chat what you are comfortable writing there, and keep the saved original-to-new path list somewhere you control.

## Limitations

This produces a document, not an act. It does not give anyone live access to storage, connect to a service, or schedule sorting. Deletion defaults to NO. Any batch size, overwrite or cross-folder move needs your explicit approval before it happens.

## FAQ

**Can I reuse this with a different photo collection?** Yes. Start a fresh chat, answer the eight questions again for the new root folder, and check the ten headings against your new answers.

**The helper already moved files and something looks wrong — does this fix it?** No. The brief includes an undo plan you follow yourself, typically a saved list of original-to-new paths plus manual move-back. Keep that list before any sorting begins.

## Source and thanks

Original TokRepo prompt (CC BY 4.0), category: everyday agents. Reference context: [ChatGPT release notes](<https://help.openai.com/en/articles/6825453-chatgpt-release-notes>) (reviewed 2026-10-04). The worked example in the prompt is fictional and shown for shape only. Source reviewed; runtime not tested — no command or tool was executed.

## Complete reusable prompt

You are helping me write a SAFETY BRIEF that I will hand to an image-sorting assistant (a person or an agent) before any file is moved, renamed or deleted. This brief is preparation only. Nothing in this prompt moves files, opens folders, browses my device or contacts anyone. I will perform or approve every action later.

## What to collect from me first
If I have not provided the items below, pause and ask me for them one at a time. Do not guess folder names, file counts or rename rules.
1. The single root folder I am willing to let the helper work inside (full path).
2. Any subfolders that must stay untouched ("do not enter" list).
3. How I currently name image files (one or two real-looking examples of the pattern).
4. How I want them named after sorting (target pattern), including date order and separators I use.
5. The destination subfolders I want images sorted into, with a short plain-language rule for each.
6. What should happen to files that match nothing.
7. Whether deletion is allowed at all. Default answer is NO.
8. My preferred undo method: manual move-back, a saved list of original-to-new paths, or a copy-first approach where originals stay in place.

## Task
Write the brief in this exact order, using my answers verbatim where I gave them and the label [NEEDS MY INPUT] where I did not:

1. Scope statement — one sentence naming the root folder and stating that nothing outside it may be read, moved or renamed.
2. Allowed folders — a numbered list. Mark each as read-only or read-and-sort.
3. Off-limits folders — a numbered list, with the instruction that the helper must stop and ask if a task seems to require them.
4. Rename pattern — show my current pattern, the target pattern, and one worked example built only from the patterns I supplied. Flag any character or ordering ambiguity I should resolve.
5. Sorting rules — one line per destination folder: condition, example filename that would land there.
6. Catch-all behavior — state clearly what happens to unmatched files.
7. Deletion policy — restate YES or NO, and if NO, say that the helper must never delete or empty anything and should instead list candidates for me to review.
8. Undo plan — a numbered recovery procedure a non-expert could follow, including where the original-to-new path list is stored and how to verify a restore worked.
9. Stop-and-ask list — actions requiring my explicit approval first: crossing folders, overwriting, deleting, renaming files whose pattern does not match, and any batch over the limit I give.
10. Dry-run request — ask the helper to first report what it WOULD do and make no changes until I approve.

## Output format
Markdown with the ten numbered headings above. Keep it under one page. Put [NEEDS MY INPUT] inline, not in a separate section. End with a three-line "Before I approve" checklist I can tick off.

## Uncertainty and missing input
If two of my answers conflict, say so plainly and ask which wins. Never invent a folder, a rename rule, a file count or a permission I did not give. If I did not specify unmatched-file behavior, default to "leave in place and list them" and label it as a default I can change.

## Review checks before any file action
- Every folder named is inside the root I approved.
- No delete step appears unless I explicitly said deletion is allowed.
- The rename example uses only characters and separators from my target pattern.
- The undo plan can be followed without the helper being present.
- The stop-and-ask list covers overwrite, delete, cross-folder and oversized-batch cases.

## Boundaries
This brief prepares instructions only. It does not give the helper live access, does not connect to any storage service, and does not schedule or perform sorting. I remain the person who approves and, if I choose, executes each action.

---
Worked example (fictional, for shape only):
Input: root = /home/me/Photos; off-limits = /home/me/Photos/Tax; current names like IMG_2043.jpg; target pattern like 2024-06-14_trip_001.jpg; destinations Trip, Family, Receipts, Unsorted; unmatched = leave in place and list; deletion = NO; undo = saved path list plus manual move-back.
Output shape (abridged): "1. Scope: only /home/me/Photos... 3. Off-limits: Tax — stop and ask... 4. Rename: IMG_2043.jpg -> 2024-06-14_trip_001.jpg (date source [NEEDS MY INPUT])... 7. Deletion: NO — list candidates only... 10. Dry run: report planned moves first."
Pass/fail checks for this example: PASS if the Tax folder appears in off-limits and every destination lies under /home/me/Photos; FAIL if any step deletes or if the rename example introduces a separator I never supplied.

## References and reuse

- [ChatGPT release notes](https://help.openai.com/en/articles/6825453-chatgpt-release-notes) · Reviewed 2026-10-04

Original TokRepo prompt · [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/). Reference documents retain their own rights.

---

<!-- ZH -->

# 让智能体整理图片前的安全交接说明

一个可复用的提示词，把你关于文件夹、重命名和撤销方式的回答整理成一页交接说明，供整理图片的助手遵守。

## 开始使用

**粘贴什么：** 把下面完整提示词复制到一个能接受文字的普通 AI 对话里。在此之前，先粘贴你自己对八个问题的回答。如果有哪一项没答，提示词会要求助手写上 `[NEEDS MY INPUT]`，而不是自行猜测。

**粘贴到哪里：** 任何能与 AI 助手进行文字对话的地方。不需要终端、账号设置或上传文件。

**如何检查输出：** 回复应当是 Markdown，含十个编号标题，大约一页之内，并以三行“批准之前”清单结尾。用你自己的回答逐项对照：

| 检查项 | 应当满足 |
|---|---|
| 范围 | 只写你批准的一个根文件夹 |
| 禁区清单 | 包含你指定不可触碰的文件夹 |
| 重命名示例 | 只使用你确实提供过的分隔符 |
| 删除 | 除非你明确允许，否则显示 NO |
| 撤销方案 | 即使助手不在场也能照着做 |

这份说明只是准备工作。它不安排任何任务、不读取文件、也不发送消息。

## 用途说明

整理照片正是适合交给助手的杂活，也正是一旦靠猜就会出错的场景。这个提示词先让你回答八个短问题——根文件夹、禁区文件夹、当前与目标命名、目标文件夹、未匹配文件、删除、以及撤销方式——然后把你的回答整理成一份助手必须遵守的说明。

## 缺失输入与隐私

如果你的两个回答互相矛盾，提示词会问以哪个为准，而不是替你做选择。如果你没说明未匹配文件如何处理，它会默认“原地保留并列出清单”，并标明这是可以修改的默认值。

文件夹路径属于隐私。只把愿意写进对话的内容放进去，并把保存的“原路径到新路径”清单放在你自己掌控的地方。

## 局限

它产出的是一份文档，不是一个动作。它不会给任何人存储的实时访问权，不连接任何服务，也不安排整理。删除默认为 NO。任何批量上限、覆盖或跨文件夹移动，都必须先得到你的明确批准。

## 常见问题

**可以用在别的照片集上吗？** 可以。开一个新的对话，针对新的根文件夹重新回答八个问题，再用新的回答核对十个标题。

**助手已经移动了文件，现在有些不对劲，这能修好吗？** 不能。说明里包含的是由你自己执行的撤销方案，通常是保存好的“原路径到新路径”清单加上手动移回。请在整理开始前就保留好这份清单。

## 来源与致谢

TokRepo 原创提示词（CC BY 4.0），分类：日常智能体。参考背景：[ChatGPT release notes](<https://help.openai.com/en/articles/6825453-chatgpt-release-notes>)（2026-10-04 查阅）。提示词中的示例为虚构，仅用于展示结构。已审阅来源；未做运行时测试——未执行任何命令或工具。

## 完整可复制提示词

你正在帮助我撰写一份安全说明（SAFETY BRIEF），我会在任何文件被移动、重命名或删除之前，把它交给一位图像整理助手（一个人或一个智能体）。这份说明只是准备工作。本提示词中的任何内容都不会移动文件、打开文件夹、浏览我的设备或联系任何人。所有操作之后都将由我执行或批准。

## 首先需要向我收集的信息
如果我尚未提供以下条目，请暂停并逐条向我询问。不要猜测文件夹名称、文件数量或重命名规则。
1. 我愿意让助手在其中工作的唯一根文件夹（完整路径）。
2. 任何必须保持不动的子文件夹（“禁止进入”清单）。
3. 我当前如何命名图像文件（该模式的一到两个看起来真实的示例）。
4. 整理后我希望如何命名（目标模式），包括日期顺序和我使用的分隔符。
5. 我希望将图像整理到的目标子文件夹，并为每个子文件夹附上一条简短、通俗的规则。
6. 对不匹配任何规则的文件应如何处理。
7. 是否允许删除。默认答案为 NO。
8. 我偏好的撤销方式：手动移回、保存一份原路径到新路径的清单，或采用原件留在原处的先复制方式。

## 任务
严格按照以下顺序撰写这份说明，在我提供了回答的地方逐字使用我的回答，在我未提供的地方使用标签 [NEEDS MY INPUT]：

1. 范围声明——一句话，指明根文件夹，并声明不得读取、移动或重命名其之外的任何内容。
2. 允许的文件夹——编号列表。将每个标记为只读或可读并整理。
3. 禁区文件夹——编号列表，并附上说明：如果某项任务似乎需要用到这些文件夹，助手必须停下并询问。
4. 重命名模式——展示我当前的模式、目标模式，以及一个仅根据我提供的模式构建的示例。标出任何我应该解决的字符或排序歧义。
5. 整理规则——每个目标文件夹一行：条件，以及会落入该文件夹的示例文件名。
6. 兜底行为——清楚说明未匹配文件会如何处理。
7. 删除政策——重申 YES 或 NO，如果是 NO，说明助手绝不能删除或清空任何内容，而应列出候选项供我审核。
8. 撤销方案——一套非专家也能照着做的编号恢复流程，包括原路径到新路径的清单存放在哪里，以及如何验证恢复成功。
9. 停下并询问清单——需要我先明确批准的操作：跨文件夹、覆盖、删除、重命名模式不匹配的文件，以及任何超过我给定上限的批量操作。
10. 试运行请求——请助手先报告它将会做什么，在我批准之前不做任何更改。

## 输出格式
使用 Markdown，包含上述十个编号标题。控制在一页以内。将 [NEEDS MY INPUT] 内联放置，不要放在单独章节。以一份我可以逐项勾选的三行“批准之前”清单结尾。

## 不确定与缺失输入
如果我的两个回答互相冲突，请如实指出，并询问以哪个为准。绝不能编造我没有给出的文件夹、重命名规则、文件数量或权限。如果我未指定未匹配文件的处理方式，默认采用“原地保留并列出清单”，并标明这是我可以更改的默认值。

## 任何文件操作之前的复核检查
- 提到的每个文件夹都在我批准的根文件夹之内。
- 除非我明确说过允许删除，否则不出现删除步骤。
- 重命名示例只使用目标模式中的字符和分隔符。
- 即使助手不在场，也能照着执行撤销方案。
- 停下并询问清单覆盖覆盖、删除、跨文件夹和批量过大这些情况。

## 边界
这份说明只准备指令。它不会给助手实时访问权，不连接任何存储服务，也不安排或执行整理。仍然由我批准，并在自己选择时，执行每一项操作。

---
示例（虚构，仅用于展示结构）：
输入：根目录 = /home/me/Photos；禁区 = /home/me/Photos/Tax；当前名称类似 IMG_2043.jpg；目标模式类似 2024-06-14_trip_001.jpg；目标文件夹 Trip、Family、Receipts、Unsorted；未匹配 = 原地保留并列出清单；删除 = NO；撤销 = 保存的路径清单加手动移回。
输出形态（节选）：“1. 范围：仅 /home/me/Photos…… 3. 禁区：Tax——停下并询问…… 4. 重命名：IMG_2043.jpg -> 2024-06-14_trip_001.jpg（日期来源 [NEEDS MY INPUT]）…… 7. 删除：NO——仅列出候选…… 10. 演练：先报告计划移动。”
此示例的通过/失败检查：如果 Tax 文件夹出现在禁区中，且每个目标文件夹都位于 /home/me/Photos 之下，则为 PASS；如果任何步骤发生删除，或重命名示例引入了我从未提供过的分隔符，则为 FAIL。

## 参考资料与复用

- [ChatGPT release notes](https://help.openai.com/en/articles/6825453-chatgpt-release-notes) · Reviewed 2026-10-04

TokRepo 原创提示词 · [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/)。参考资料保留各自原有权利。

---
Source: https://tokrepo.com/en/workflows/safety-brief-before-agent-sorts-your-images-c84b0798
Author: Prompt Lab