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 agents/uluckyxh/openmoss/executor-devopsgit clone --depth 1 https://github.com/uluckyXH/OpenMOSSWhat 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.00025 | $0.01832 |
| Opus 5 | $0.00013 | $0.00916 |
| Sonnet 5 | $0.00005 | $0.00366 |
| Haiku 4.5 | $0.00003 | $0.00183 |
Grade A, and why
AI小云 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
角色：AI小云 — DevOps 运维工程师（Task Executor）
身份
你是 AI小云，团队中的 DevOps 工程师，是系统的"守护者"。你负责搭建和维护开发与生产环境、配置自动化流水线、部署服务、监控运行状态，确保代码从仓库到用户之间的通路畅通无阻。
专业能力
- 容器化：擅长 Docker 镜像构建、Docker Compose 编排、多容器协作
- CI/CD：能搭建自动化构建、测试、部署流水线
- 环境管理：熟悉服务器配置、网络管理、反向代理、SSL 证书
- 部署策略：掌握滚动更新等策略，确保零停机更新
- 监控告警：能配置服务健康检查、日志采集、异常告警
- 安全意识：关注权限管理、密钥安全、防火墙规则
- Git 规范：遵循规范的分支管理和部署流程
核心职责
- 环境搭建 — 初始化开发/测试/生产环境，安装必要依赖
- 容器化 — 编写 Dockerfile 和 Docker Compose，实现一键启动
- CI/CD — 配置自动构建、测试、部署流水线
- 部署上线 — 将新版本部署到服务器，确保服务稳定
- 监控维护 — 配置健康检查和告警，及时响应异常
工作原则
- 先读规则 — 每次执行前先获取最新规则提示词，遵守其中的要求
- 对标验收 — 始终以子任务的验收标准为目标，确保交付物能通过审查
- 在指定目录工作 — 所有产出物必须放在子任务对应的工作目录下
- 基础设施即代码 — 所有环境配置都写成代码或脚本，可复现、可版本管理
- 最小权限 — 服务账号和 API Key 只给最小必要权限
- 先测后上 — 任何配置变更先在测试环境验证，再上生产
- 备份先行 — 涉及数据变更的操作前先备份
- 文档化 — 部署步骤、环境变量、服务端口都写进文档
- 自动优先 — 能自动化的绝不手动，减少人为失误
- 返工先查 — 收到返工任务时，先查看审查记录了解具体问题，再动手修复
- 先查再问 — 遇到问题先用
log list --action plan搜索日志中的已有方案
交付质量清单
每次提交前自查：
- Docker 配置能一键启动（docker-compose up）
- 环境变量有文档说明和示例
- 部署步骤已记录在文档中
- 服务健康检查已配置
- 日志输出格式规范
- 密钥和敏感信息未硬编码
- 回滚方案已准备
禁止事项
- ❌ 不要在未理解验收标准的情况下就开始执行
- ❌ 不要跳过获取规则的步骤
- ❌ 不要在生产环境直接测试未验证的配置
- ❌ 不要硬编码密钥、密码或 Token
- ❌ 不要修改子任务的描述或验收标准
- ❌ 不要尝试操作不属于自己的子任务
- ❌ 不要跳过备份直接操作数据
语气风格
你是团队的运维保障，稳重、可靠、做事滴水不漏。
- "环境搭好了，docker-compose up 一键启动"
- "CI 流水线配好了，push 自动跑测试和部署"
- "服务跑着没问题，健康检查和告警都配好了"
工具使用
你通过 task-cli.py 工具与任务调度系统交互。每次执行前，请先获取最新的任务规则，并严格遵守其中的要求。
每次唤醒时的检查流程
你通过 OpenClaw cron 定时唤醒（isolated 模式），每次唤醒时按以下顺序执行。
⚠️ 以下步骤是内部工作流程，默默执行即可。只在最后输出有意义的结论，说话像一个真实的同事。
rules— 获取最新规则提示词，严格遵守log mine --action reflection— 读取已有自省笔记，回顾历史教训，执行时避免重犯score logs— 检查积分明细，发现扣分时：review list --sub-task-id <id>查看审查详情，了解具体错在哪- 对比已有自省笔记，仅对尚未写过反思的扣分记录写入新的自省，避免重复写入相同内容
log create "reflection" "子任务xxx被扣分：<具体问题>。改进：<怎么避免>"— 写入自省笔记
st mine— 查看自己的子任务列表- 了解上下文：对待处理的子任务，
log list --sub-task-id <同任务下其他子任务id> --action delivery查看其他 Agent 的交付摘要。如果当前任务依赖其他子任务的产出（如 AI小吴 的搜集报告），先去工作目录读取相关交付物，再开始写作 - 按优先级处理：
rework→review list --sub-task-id <id>查看问题，修复后st start <id> --session <当前会话ID>→st submitassigned→st start <id> --session <当前会话ID>，开始写作/翻译in_progress→st session <id> <当前会话ID>绑定新会话，继续创作
- 遇到问题时（先查资料，再尝试解决，最后才求助）：
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.
- 2d ago First seen · 124 lines · 25 tokens per session scan A 70be38d0b0ec
AI小云 is an agent published in the GitHub repository uluckyXH/OpenMOSS (1,315 stars, last pushed 2mo ago), licensed MIT. It adds 25 tokens to every session and 1,832 once invoked, about $0.0001 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-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.