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 skills/ozzy-labs/suasor/task-updatenpx skills add ozzy-labs/suasor --skill task-updategit clone --depth 1 https://github.com/ozzy-labs/suasorWrote 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/skills/ozzy-labs/suasor/task-update)<a href="https://agentmods.dev/skills/ozzy-labs/suasor/task-update"><img src="https://agentmods.dev/badge/skills/ozzy-labs/suasor/task-update.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.00099 | $0.00823 |
| Opus 5 | $0.00049 | $0.00411 |
| Sonnet 5 | $0.00020 | $0.00165 |
| Haiku 4.5 | $0.00010 | $0.00082 |
Grade A, and why
task-update 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
task-update
task の lifecycle 状態を遷移させる HITL write skill。task.create が task を開き（proposed）task.list が読むのに対し、本 skill は in_progress / completed / dropped への前進（および再開）を担う（ADR-0004）。next-actions / brief が読む state を実際に動かす経路。
いつ発火するか
- 「これ終わった」「完了にして」「あのタスク done」（→
completed） - 「task を進行中に」「着手した」（→
in_progress） - 「これは見送り」「やめる」（→
dropped） - 「task を再開」「やっぱりやる」（→
open/in_progress）
何をするか（MCP tool flow）
read で特定して、write は HITL。auto-apply 経路は存在しない（ADR-0004）。
task.list（stateで絞り可、updatedAfter/updatedBeforeで期間絞り）で対象 task を特定する。各 task はid/title/state/updated_at- どの task をどの状態にするかユーザーに提示して確認を取る（native framing: ホスト側で人の承認を促す）
- 承認後、
task.update（taskId/state）で遷移させる（TaskAppliedを append →tasksprojection）。state 語彙:open/in_progress/completed/dropped
制約
- HITL。人の承認なしに
task.updateを呼ばない。auto-apply しない。task.listは read（特定） - idempotent: 同じ state への遷移は no-op（
unchanged、event を append しない）。存在しない task はmissing（status で報告、throw しない） - lifecycle に禁止遷移は無い（
completedの task をin_progressに戻す等も可）。新規 task の作成はtask.create（別 skill / 経路） - 本 skill は手順書のみで実処理を持たない
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 · 49 lines · 99 tokens per session scan A 9d8a1896bcff
task-update is a skill published in the GitHub repository ozzy-labs/suasor (0 stars, last pushed 25d ago), licensed MIT. It adds 99 tokens to every session and 823 once invoked, about $0.0005 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.
Other skills, from other repositories
run-task
Execute a single Todo task through In Progress to Review, meeting every acceptance criterion with tests and vibe-lint checks. Refuses Planning-status tasks. Invoked as /agiflow:run-task . Uses gettask, updatetask, createtaskcomment.
state-trees
Create, inspect, and edit StateTree assets — states, tasks, transitions, conditions, considerations, and property bindings for AI behavior and game logic (StateTreeService). Use when the user asks to build a StateTree, add states/tasks/transitions, bind task properties, set up Utility AI considerations, or wire…
task-loop
任务目标驱动执行闭环预装 skill,整合任务识别/规划/派发搜推/验收/BBS 接力/arch 场景规划变体(planning-arch)与架构师名册 mock(arch-analysis)共七段为单一 skill,预装到所有 bot 等同各段单独安装到对应 bot;各段按各自触发词自门控仅命中段执行(用户面 /task 或 [RESUMETASK] 或副屏标签命中识别;框架 [planning] 命中规划,arch 场景含「某某某公司」命中 planning-arch 变体;框架 [search] 命中派发搜推;worker 叶子自验收命中验收;引擎 BBS 通知命中接力,其 scoped 叶子 instruction…
bbs-relay-pickup
被唤醒时从 task API 发现 BBS 升级任务、CAS 占根、自判剩余、挂节点、执行、经回投写回.
task-planning-arch
计算任务 gap 并产出下一步可执行子任务 List[TaskSpec];gap 已闭返回空数组。对齐 arch 场景(架构师名册/技术栈概览/双视角分析)确定式分解——按根目标交付物集合 + donechildren 查表(参照 task-planning storage 特例,非自由 LLM 分解)。.
task-search
在框架预查的候选 bot 集里决出执行者(who)与协作方式(how),返回 4 态 SearchResult(HITSINGLE/HITGROUP/HITMULTIBOTS/MISS)。对齐案例剧本确定式映射。.