take

A workflow command for taking ownership of an assigned work item, carrying it through its required steps, and returning evidence when it is finished. A workflow is a defined sequence of statuses and checks for completing work.

In plain words
What is it for?
Use it to read an assigned work item, start it after prerequisites are met, coordinate implementation, attach results, update its status, and report outstanding work.
Why use it?
It keeps execution tied to the assigned item, requires unresolved questions to be addressed first, and records completion evidence and the related commit or review request.

Command

Install

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.

agentmods
npx agentmods add commands/go1c/workflow-plugin/take
Clone the repo
git clone --depth 1 https://github.com/Go1c/workflow-plugin
Per session 30 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 403 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00030 $0.00403
Opus 5 $0.00015 $0.00201
Sonnet 5 $0.00006 $0.00081
Haiku 4.5 $0.00003 $0.00040

Measured yesterday against content hash 09124015efa9, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

take 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 yesterday.

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.

commands/take.md · 14 lines

What it actually says

调起 workflow-execute 技能承接下面的单。先判定执行模式(自持凭证直连,或无凭证由调度方代写——当前目录没有 .workflow 绑定时禁止靠全局 profile 兜底写数据);读单按「正文 + 评论 + 附件 + 验收项」拉全,前置未满足就停下报告;开工前先梳理需求,把歧义与需要拍板的决策点连同建议一并摆出来讨论,全部有答复才现查 transitions 流转到进行中;干活阶段按讨论确认的拆分尽可能并行子 Agent(互斥所有权切分,子 Agent 不碰凭证与回写);完成后按统一证据评论模板回写(遗留补单 → 附件 → 评论 → 流转状态,每步读回):评论必带提交单号(Git commit / PR 或 SVN revision)、这次不做的 TODO 经确认补需求单并引用单号、流转以待验收优先(工作流无验收态才选已完成),再按交回格式汇报。

预设边界:只承接指定的单 —— 不建新单、不动别人的卡、不改原始描述、不验收自己的交付、不跳过讨论直接开工。

完成后的状态、证据评论、附件和依赖写回先进入本地 bundle,再由当前权限模式上传和读回;评论仍必须带提交单号,遗留项仍需补需求单并引用单号。

单号或派遣内容:

$ARGUMENTS

Changes

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.

  1. yesterday First seen · 14 lines · 30 tokens per session scan A 09124015efa9

Subscribe to this mod's changes

take is a command published in the GitHub repository Go1c/workflow-plugin (2 stars, last pushed 2d ago), licensed MIT. It adds 30 tokens to every session and 403 once invoked, about $0.0002 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-31.