可复制的 Agent 规则
把 Deno 权限、依赖、验证和危险操作边界写入仓库指令
将下面规则按仓库实际情况裁剪后放进 AGENTS.md：
## Deno workflow
- Read deno.json/deno.jsonc, deno.lock, package.json, and CI before changing commands.
- Reuse existing imports and tasks. Do not invent configuration keys.
- Add packages with the repository's Deno CLI workflow; keep one reviewed lockfile diff.
- Grant only scoped --allow-* permissions. Never use -A merely to make a command pass.
- Treat --allow-run and --allow-ffi as sandbox escape boundaries.
- After changes run: deno fmt --check, deno lint, deno check, and relevant deno test targets.
- Report exact commands and failures; do not claim tests you did not run.
- Ask before deleting lockfiles, changing major versions, publishing, or deploying.
仓库需要补充的事实
- Deno 固定版本和升级流程；
- 权威配置文件与 workspace 根；
- dev、test、check、build、deploy 的现有 task 名；
- 哪些网络主机、路径和环境变量允许授权；
- 是否兼容
package.json/node_modules； - 生产平台与回滚流程。
规则不能代替执行权限控制。CI、容器和部署平台仍要实施最小权限与审批。