agent-task-confirm skillA
agent-task-confirm is agent-read markdown (skill) from aaaaqwq/agi-super-team: Use when confirming whether a dispatched agent task was actually received, activated, and progressing after sessions_send or other task handoff actions..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Agent 任务派发与确认机制 确保每次派发任务后，agent 确实收到并在执行。 ## 触发条件 - 每次通过 sessions_send 派发任务后自动执行 - "检查员工状态"、"任务确认" ## 派发后确认流程 ### Step 1: 派发任务 ``` sessions_send(sessionKey="agent:<id>:telegram:group:-1003890797239", message="【CEO指令】...") ``` ### Step 2: 立即确认送达（30秒内） ``` sessions_list(activeMinutes=5, kinds=["agent"], messageLimit=0) ``` 检查目标 agent 的 session 是否 active（updatedAt 在最近 60 秒内）。 ### Step 3: 判断状态 | 状态 | 判断条件 | 处理 | |------|----------|------| | ✅ 已接收 | session active, updatedAt 刚更新 | 等汇报 | | ⚠️ 可能卡住 | session active 但 5min+ 无新消息 | 发催促消息 | | ❌ 未接收 | session 不在 active 列表 | 重发一次，仍失败则报告 Daniel | ### Step 4: 超时催促（5分钟无汇报） 如果 agent 5 分钟内没有发群里汇报，发催促： ``` sessions_send(sessionKey="agent:<id>:...", message="【催促】你的任务完成了吗？立即用 message 发群里汇报进度。") ``` ### Step 5: 死亡判定（10分钟无响应） 如果催促后 5 分钟仍无反应： 1. 检查 agent 的 session 是否报错（abortedLastRun） 2. 报告 Daniel："小X 可能卡住了，需要检查" 3. 考虑重新派发给其他 agent ## 每次派发的标准模板 任务消息必须包含： 1. 【CEO指令】开头 2. 具体任务描述 3. 文件写在哪里 4. 完成后的 message 汇报指令（含 accountId） 5. "不发群里 = 任务没完成" ## 批量检查命令 快速检查所有 agent 状态： ``` sessions_list(activeMinutes=10, kinds=["agent"], messageLimit=1) ``` 看每个 agent 的 updatedAt 和最后一条消息判断是否在工作。
Read the whole file at its exact version.
How to install
mdr add aaaaqwq/agi-super-team/agent-task-confirm@git:20260331.eeacae6mdr add aaaaqwq/agi-super-team/agent-task-confirm@sha256:146616e547f69b40Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_alan2ic4yg7vepdx)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260331.eeacae6 latest | 2026-03-31 | eeacae6 | 2,054 B | A | view · diff |
| git:20260316.7e00aec | 2026-03-16 | 7e00aec | 1,834 B | C | view · diff |
| git:20260309.5eff0c2 | 2026-03-09 | 5eff0c2 | 1,838 B | C | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (2054 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
aaaaqwq/agi-super-team · 98 stars · license MIT · pushed 2026-09-23 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_alan2ic4yg7vepdx GET https://markdownregistry.com/api/v1/resolve?ref=aaaaqwq/agi-super-team/agent-task-confirm GET https://markdownregistry.com/api/v1/blob/146616e547f69b4076c306a6d4676f6038754afc558de7b7e15aac6662c010f7
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.