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 rules/povli/agentgod-oss/agent-orchestratorgit clone --depth 1 https://github.com/povli/AgentGOD-ossWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/rules/povli/agentgod-oss/agent-orchestrator)<a href="https://agentmods.dev/rules/povli/agentgod-oss/agent-orchestrator"><img src="https://agentmods.dev/badge/rules/povli/agentgod-oss/agent-orchestrator.svg" alt="Measured on agentmods" height="20"></a>What 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.00000 | $0.00592 |
| Opus 5 | $0.00000 | $0.00296 |
| Sonnet 5 | $0.00000 | $0.00118 |
| Haiku 4.5 | $0.00000 | $0.00059 |
Grade A, and why
agent-orchestrator 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 4d 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.
What it actually says
AgentGOD 上下文检查点协议
状态文件格式
所有工作流状态文件位于 workflows/state/，采用 Markdown + YAML frontmatter：
---
workflow_id: string # 格式: {描述}-{YYYYMMDD-HHmmss}
status: string # in_progress | waiting_for_input | completed | failed
created_at: ISO-8601
updated_at: ISO-8601
current_phase: string # 当前执行阶段
assigned_agents: [string] # 参与的 Agent 列表
---
检查点触发条件
子 Agent 应在以下情况保存检查点并返回 ## CHECKPOINT：
- 阶段边界：一个明确的子步骤完成，即将进入下一步
- 输出量大：已生成的内容超过预估的 60%
- 长迭代：已执行超过 8 轮工具调用
- 外部依赖阻塞：等待某个外部操作完成
CHECKPOINT 返回格式
## CHECKPOINT
### 已完成
（当前步骤的完整输出）
### 待继续
（下一步的具体任务描述）
### 关键上下文
（续接时必须的变量、文件路径、决策记录）
续接协议
指挥官检测到 CHECKPOINT 后：
- 将 CHECKPOINT 内容追加到对应的 state 文件
- 更新 state 文件的
updated_at和current_phase - 发起新 Task，prompt 结构：
你是 {Agent.name}，继续之前的工作。
请先读取状态文件：{state_file_path}
找到最后一个 CHECKPOINT，从"待继续"部分开始执行。
## 当前子任务
{原始子任务描述}
NEEDS_INPUT 状态
当子 Agent 返回 ## NEEDS_INPUT 时：
- state 文件的 status 更新为
waiting_for_input - 暂存状态写入 state 文件
- 用户回答后 status 恢复为
in_progress
状态清理
- 完成的工作流：state 文件保留，status 标记为
completed - 失败的工作流：state 文件保留，status 标记为
failed，附带错误信息 - 建议在
.gitignore中添加workflows/state/避免提交运行时状态
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.
- 4d ago First seen · 80 lines · 0 tokens per session scan A 77a4bac99ef9
agent-orchestrator is a cursor rule published in the GitHub repository povli/AgentGOD-oss (6 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 592 tokens. 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-31.
Other cursor rules, from other repositories
mempalace-recall-always
Always-on MemPalace recall — search the palace before answering about past work, people, projects, or prior decisions.
dreamd-recall
Recall lessons, decisions, and prior context from the .agent/ memory daemon. Use when starting work in a project that has a .agent/ folder, when the user references a past decision, or when you are about to make a choice that has a documented prior.
session-memory
Use at conversation wrap-up or when the user explicitly indicates end-of-session — capture residual lessons not captured in-flight.
common_memory_bank
I am Cursor, an expert software engineer with a unique characteristic: my memory resets completely between sessions. This isn't a limitation - it's what drives me to maintain perfect documentation. After each reset, I rely ENTIRELY on my Memory Bank to understand the project and continue work effectively. I MUST read…
context-recorder-system
Context Recorder System (记录员系统) - 模块化索引文件.
memsprout
Cursor rule "memsprout" from memsprout/agents, covering using memsprout, search first, capturing, spaces and topics and files.