📦 Safe Long-Run Mode GPT5.4 — Safe工具
v1.0.0[AI辅助] Operate long-running tasks safely when the environment is optimized for GPT-5.4 as the primary and often only model. Use when the user wants a low-cost, high...
0· 95·0 当前·0 累计
by 安全扫描
OpenClaw
安全
high confidenceThis is an instruction-only skill that gives procedural guidance for running long tasks on GPT-5.4 and does not request credentials, install software, or contain hidden code — its requirements and instructions are coherent with its stated purpose.
评估建议
This skill is a text-only operating procedure for running long tasks on GPT-5.4 and, by itself, poses minimal installation risk. Before using it in live runs, be prepared to: (1) deny or carefully scope any runtime requests for credentials to external services (Azure, GitHub, Microsoft Graph, etc.); (2) review and control what artifacts the agent writes or uploads (use least privilege and restricted folders); (3) monitor any autonomous actions (the platform allows autonomous invocation by defaul...详细分析 ▾
✓ 用途与能力
Name and description match the content of SKILL.md: the skill is a runtime operating procedure for long-running GPT-5.4 workflows. It does not request unrelated binaries, env vars, or config paths.
ℹ 指令范围
Instructions stay within orchestration best-practices: split tasks, checkpoint, use subagents, and treat external APIs as bottlenecks. The guidance is operationally broad (delegation, use of external services, writing artifacts), which is expected for an orchestration/operating-mode doc but grants the agent discretion at runtime to interact with files and external APIs. There are no explicit instructions to read unrelated system files or exfiltrate data.
✓ 安装机制
No install spec and no code files — nothing is written to disk or fetched at install time. This is low-risk for installation.
✓ 凭证需求
The skill declares no required environment variables or credentials. It references external services (Azure, GitHub, Microsoft Graph, Orgo) as potential bottlenecks, which is reasonable context for orchestration guidance but means the agent may later request or use credentials when executing concrete tasks; those requests would be separate and should be evaluated when they arise.
✓ 持久化与权限
Flags: always is false and the skill is user-invocable (normal). It does not request persistent presence or attempt to modify other skills or system-wide configs.
安全有层次，运行前请审查代码。
运行时依赖
无特殊依赖
版本
latestv1.0.02026/3/27
Initial release — GPT-5.4-only operating mode for long-running tasks
● 无害
安装命令
点击复制官方npx clawhub@latest install safe-long-run-mode-gpt54
镜像加速npx clawhub@latest install safe-long-run-mode-gpt54 --registry https://cn.longxiaskill.com
技能文档
Use this skill when GPT-5.4 is the default operating model for both orchestration and delegated work.
Core rule
Use GPT-5.4 for long work by making tasks cheap, segmented, and resumable. Since the model layer is cost-efficient, the real risks are provider throttling, session interruption, and lack of checkpoints.当...时 到 使用 mode
Use it when:- 用户 wants 到 minimize 模型 cost
- task implementation-heavy
- task file-heavy 或 repetitive
- multiple subagents 可能 involved
- external services 可能 throttle
- quality depends 更多 在...上 process discipline 比 premium 模型 nuance
Operating procedure
1. 路由 到 GPT-5.4 由 默认
Use GPT-5.4 for:- coding
- docs
- research
- skills
- website work
- project tracker updates
- internal tooling
- multi-agent delegated work
- long build/test loops
Do not escalate to another model unless the user asks or the task clearly requires premium polish/judgment.
2. Split work aggressively
Break long tasks into explicit phases and write down the next step before moving on.Preferred phases:
- inspect
- plan
- execute
- 验证
- 举报
3. 保存 progress continuously
Always leave artifacts that make recovery easy:- notes
- drafts
- partial outputs
- checkpoint files
- project updates
- 结果 summaries
4. 使用 subagents 作为 workers
For large or parallel tasks, use subagents to keep the main thread clean. Delegate when:- tasks independent
- multiple files 或 systems involved
- work 可能 take 当...时
- specialized roles improve throughput
5. Treat external APIs 作为 真 bottleneck
In GPT-5.4-only mode, model cost is not the main concern. External limits are. Be careful with:- Azure / Microsoft 图形
- ClawHub / GitHub-backed operations
- Orgo runtime 和 VM usage
- websites / browser automation
- messaging providers
Use batching, backoff, and fewer larger writes.
6. 使 every task resumable
If interrupted, resume from artifacts instead of recreating work. Always know:- 什么 已经 已完成
- 什么 file contains latest state
- 什么 exact 下一个 action 应该 happen
Ideal GPT-5.4-仅 使用 cases
- codebase changes
- documentation builds
- repeated content generation
- Azure script development
- internal automation
- multi-agent production work
- long back-office workflow creation
什么 到 tell 用户
Explain that GPT-5.4-only safe mode works because:- 模型 cost stays low
- throughput stays high
- reliability comes 从 checkpoints, 不 从 one giant run
- external APIs, 不 tokens, usually become limiting factor
Failure handling
If interrupted:- summarize 已完成 work
- cite saved files
- state 恢复 point
- continue 从 最后的 checkpoint
References
- 读取
references/checklist.md对于 pre-flight checklist 和 GPT-5.4 operating pattern.