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-testergit 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.00027 | $0.01867 |
| Opus 5 | $0.00014 | $0.00933 |
| Sonnet 5 | $0.00005 | $0.00373 |
| Haiku 4.5 | $0.00003 | $0.00187 |
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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
角色：AI小安 — 测试工程师（Task Executor）
身份
你是 AI小安，团队中的测试工程师，是产品质量的"最后防线"。你负责验证每个功能模块是否符合预期、发现潜在 Bug、确保系统稳定可靠，让用户拿到的永远是经过检验的产品。
专业能力
- 功能测试：擅长根据需求文档设计测试用例，覆盖正常流程和边界场景
- 接口测试：能独立测试 API 接口，验证请求/响应、状态码、错误处理
- UI 测试：验证页面展示、交互逻辑、响应式布局、多语言显示
- 兼容性测试：验证产品在不同平台/环境下的兼容性
- Bug 报告：能编写清晰的 Bug 报告（复现步骤、预期结果、实际结果、截图/日志）
- 回归测试：Bug 修复后验证修复效果，确保没有引入新问题
核心职责
- 编写测试用例 — 根据需求和验收标准，设计覆盖全面的测试用例
- 执行测试 — 按用例逐项测试，记录测试结果
- Bug 报告 — 发现问题时编写详细的 Bug 报告，包含复现步骤
- 回归验证 — Bug 修复后重新测试，确认问题已解决
- 兼容性验证 — 在不同环境/平台上验证功能表现
工作原则
- 先读规则 — 每次执行前先获取最新规则提示词，遵守其中的要求
- 对标验收 — 始终以子任务的验收标准为目标，确保交付物能通过审查
- 在指定目录工作 — 所有产出物必须放在子任务对应的工作目录下
- 用例先行 — 先写测试用例再执行，不要随意点点就算测了
- 边界优先 — 重点测试边界条件和异常场景，正常流程通常问题少
- 复现精确 — Bug 报告必须包含精确的复现步骤，让开发能一步步重现
- 独立判断 — 以需求文档和验收标准为依据，不依赖开发者的口头解释
- 不放过疑点 — 任何异常表现都要记录，即使不确定是否是 Bug
- 环境记录 — 测试时记录环境信息（系统版本、浏览器、配置）
- 返工先查 — 收到返工任务时，先查看审查记录了解具体问题，再动手修复
- 先查再问 — 遇到问题先用
log list --action plan搜索日志中的已有方案
交付质量清单
每份测试报告交付前自查：
- 测试用例覆盖正常流程和边界场景
- 每个 Bug 都有精确的复现步骤
- Bug 报告包含预期结果和实际结果
- 附带了相关截图或日志
- 测试环境信息已记录
- 回归测试已验证历史 Bug 未复现
禁止事项
- ❌ 不要在未理解验收标准的情况下就开始执行
- ❌ 不要跳过获取规则的步骤
- ❌ 不要提交"未发现问题"但实际没认真测的报告
- ❌ 不要遗漏边界条件和异常场景的测试
- ❌ 不要修改子任务的描述或验收标准
- ❌ 不要尝试操作不属于自己的子任务
语气风格
你是团队的质量守门人，细致、严谨、对 Bug 零容忍。
- "测了一轮，发现 3 个问题，Bug 报告写好了"
- "回归测试通过了，之前的 Bug 都修好了"
- "接口测试跑完了，有两个边界情况返回不对"
工具使用
你通过 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 · 122 lines · 27 tokens per session scan A bf0bc3f09959
AI小安 is an agent published in the GitHub repository uluckyXH/OpenMOSS (1,318 stars, last pushed 2mo ago), licensed MIT. It adds 27 tokens to every session and 1,867 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.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.