Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/coo1white/cool-workflownpx agentmods add commands/coo1white/cool-workflow/release-flowWrote 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/commands/coo1white/cool-workflow/release-flow)<a href="https://agentmods.dev/commands/coo1white/cool-workflow/release-flow"><img src="https://agentmods.dev/badge/commands/coo1white/cool-workflow/release-flow/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/coo1white/cool-workflow/release-flow"><img src="https://agentmods.dev/badge/commands/coo1white/cool-workflow/release-flow.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00020 | $0.00596 |
| Opus 5.5 | $0.00008 | $0.00238 |
| Sonnet 5.5 | $0.00004 | $0.00119 |
| Haiku 4.5 | $0.00002 | $0.00060 |
Grade A, and why
release-flow 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.
What it actually says
Run the cool-workflow portable release flow. This is the multi-platform sibling
of /release: the orchestration lives in one zero-dependency script and the
independent review is DELEGATED to whatever agent you configure, so the exact
same flow runs under Claude, Codex, Gemini, OpenCode, or a plain shell.
Steps:
-
Configure the reviewer agent for THIS host (Claude):
export CW_AGENT_COMMAND="claude -p --permission-mode acceptEdits {{input}}" export CW_AGENT_MODEL="claude-opus-4-8" # optional; the agent picks otherwise # acceptEdits lets the headless reviewer WRITE its verdict file; without it the # review runs but the verdict can't be persisted and the flow fails closed at # [3/3]. The reviewer CLI must also be logged in (claude auth login). -
Run the flow in check mode (gate + independent review, no mutation):
node plugins/cool-workflow/scripts/release-flow.mjs --checkIt runs
scripts/release-gate.mjs, then spawns the configured agent (argv-style, shell:false — CW holds no key) to review the candidate and write.cw-release/review-<HEAD>.verdict. The flow fails closed unless the verdict begins withAPPROVED.
Report the JSON summary from step 2 (verdict, capability) and stop at
the first failure. Do not write the verdict file yourself — the delegated
reviewer is the only writer, and release-gate.yml re-checks it in CI.
Stop here. Do NOT run release-flow.mjs --cut yourself, on this host or
any other — cutting a tag needs CW_RELEASE_VERDICT_PRIVKEY, the ed25519
signing key that stays with the release operator and must never be read
or held by an agent (see AGENTS.md's "Shipping a release" section). Once
review is green, tell the user the candidate is ready and that the
operator cuts it themselves:
npm run release -- <x.y.z>
(plugins/cool-workflow/scripts/release-oneclick.mjs, the normal path) or,
for manual control on a non-npm host, the lower-level command run by the
operator in their own shell:
node plugins/cool-workflow/scripts/release-flow.mjs --cut --version <x.y.z> --push
See docs/release-tooling.7.md for the per-platform CW_AGENT_COMMAND presets
(Codex / Gemini / OpenCode / DeepSeek).
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.
- yesterday Changed 3cad70b1293c
- 1mo ago First seen · 58 lines · 20 tokens per session scan A e1c8228d0839
release-flow is a command published in the GitHub repository coo1white/cool-workflow (2 stars, last pushed yesterday), licensed BSD-2-Clause. It adds 20 tokens to every session and 596 once invoked, about $0.0001 per session on Opus 5.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 commands, from other repositories
review-prs
Parallel PR triage: decide merge-worthiness, prepare rebased worktrees, fix blockers, return them for human merge.
pr-ready
Run the project's pre-commit review loop to determine whether the current branch is ready to push — lint, tests, parallel pr-review-toolkit agents plus an over-engineering audit, fix-and-re-run until convergence.
release
Release manager for frontend and mobile. Writes App Store notes, user-facing changelog, flags stale docs and landing copy. Actions: notes | changelog | docs | sync.
code-review
Review the current branch changes for bugs and style issues.
create-pr
Create a pull request with proper template discovery and population.
address-pr-feedback
Systematically address PR review comments. Fetches all threads, categorizes by status (acknowledged, silently fixed, unaddressed), and guides user through posting replies and implementing fixes with explicit approval.