workflow-ops

A tool for carrying out clearly defined one-off actions in Workflow, a project-management system. It works with requirements, bugs, tasks, searches, assignments, status changes, comments, and attachments.

In plain words
What is it for?
Use it to create or find work items, assign them, change their status, add comments or attachments, and verify the resulting records.
Why use it?
It provides controlled handling for project updates, including permission checks, safe drafts, and reading data back after a write. It avoids guessing project-specific values such as statuses or member IDs.

Skill for Claude CodeCodex

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 skills/go1c/workflow-plugin/workflow-ops
Any agent
npx skills add Go1c/workflow-plugin --skill workflow-ops
Clone the repo
git clone --depth 1 https://github.com/Go1c/workflow-plugin

Made for: Claude Code, Codex.

Per session 100 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,618 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.00100 $0.02618
Opus 5 $0.00050 $0.01309
Sonnet 5 $0.00020 $0.00524
Haiku 4.5 $0.00010 $0.00262

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

Security

Grade A, and why

workflow-ops 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.

skills/workflow-ops/SKILL.md · 76 lines

How it starts

The opening of the file, as written. The whole thing — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.

workflow-ops — 在 Workflow 里干活

硬闸门(命中即停)

以下 7 条是停止条件,不是风格建议;与正文其他要求冲突时以这里为准(出处 references/gates.md)。

# 触发条件 动作
G1 project.subdomainPrefix、实际 API Host、.workflow 所选 profile 的子域三者任一不一致;或 publicDemo=true;或 .workflow 存在却解析不出 profile 停止,转 workflow-setup 重新绑定。绝不把数据写进错误项目
G2 用户尚未针对确切的项目 + 对象清单 + 数量给出明确肯定答复,且当前模式没有有效的用户级 full standing authorization 不得 POST/PATCH。内容认可、说"不错"、说"继续"都不是写入授权;full 也只覆盖已校验的 manifest;范围一变授权即失效
G3 写操作之后没有 GET 读回,或读回未核对字段与子资源数量 不得声称「已创建 / 已修改」。部分成功如实报部分成功
G4 需要在命令、日志、报告、蓝图里出现 token 走环境变量携带;任何输出里只以 wfp_ + 前 8 位指代,绝不回显完整值
G5 出现拆 WorkItem、流转状态、建分支/Worktree、跑目标仓库测试、改代码或资产的冲动 停止。落单不等于开工,本插件只负责 PM 对象
G6 需要填工作流状态、验收类型/状态、成员 ID、缺陷自定义字段等项目自定义的值 必须现查。查不到或不唯一就留空并告诉用户,绝不猜一个值填进去
G7 要在报告里写某项验证「通过」 只写实际执行过的命令与其真实输出;没跑的写「未执行」,不得用计划中的验证冒充结果

与相邻技能的边界

用户给的是一句话、文档或尚未定型的讨论结果,并要求「梳理需求」「规划需求池」「拆多专业/多交付轨道」「安排预研与并行 wave」「生成完整 Agent 提示词」时,转 workflow-planning。它负责讨论、交付拓扑判定、模板化蓝图和独立授权后的批量落单。用户要以执行者身份「拿单 / 领任务 / 开工 / 做完交付回写」时,转 workflow-execute——那是一条完整流程,不是单次操作。

本技能只处理已经明确的单次业务操作:建一张字段已定的需求/工作项、查询、指派、流转、评论或附件。写入先按 draft-format.md 生成 .workflow-drafts/<bundleId>/ bundle,再由 workflow-uploadpermission-modes.md 执行;不得把原始想法临场扩写成一套开发计划,也不得在建单后自动启动实现。

用户要反馈的是 Workflow 平台或本插件自身的问题、体验或建议(不是往自己的项目里记单)时,转 workflow-feedback——记到自己项目走本技能的记 bug,报给平台方走 feedback,两条路不混。

前置:凭证与连接检查

完整读取 connection.md —— 凭证三级解析、/me/projects/current 的分工、写操作三方一致性防呆、真值分层与失败处置表都在那里,是 setup / ops / planning 共用的单一真相源,不要凭记忆重写。

要点:先 GET $WORKFLOW_API_BASE/me 验证身份,再 GET $WORKFLOW_API_BASE/projects/current 验证 Host 解析出的项目与 membership 角色/权限。任一不通(401/403/204/404、网络失败或没有配置)→ 转 workflow-setup 技能处理,本技能不修配置。

写操作前按 connection.md 逐条过防呆检查(对应 G1),并读取有效权限模式;连接、全局查重和依赖分析可以自动执行,线上写入必须交给上传器。上传器默认以 concurrency=4 的有界 worker pool 并发独立操作,单目标资源按锁串行并逐项读回。

Read the full file on GitHub · 76 lines

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 · 76 lines · 100 tokens per session scan A 42762c9e34cf

Subscribe to this mod's changes

workflow-ops is a skill published in the GitHub repository Go1c/workflow-plugin (2 stars, last pushed 2d ago), licensed MIT. It adds 100 tokens to every session and 2,618 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.