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 commands/coo1white/cool-workflow/release-flowgit clone --depth 1 https://github.com/coo1white/cool-workflowWhat 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.00020 | $0.00591 |
| Opus 5 | $0.00010 | $0.00296 |
| Sonnet 5 | $0.00004 | $0.00118 |
| Haiku 4.5 | $0.00002 | $0.00059 |
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 2d 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
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.js --checkIt runs
scripts/release-gate.js, 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.js --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.js, 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.js --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.
- 2d 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 6d ago), licensed BSD-2-Clause. It adds 20 tokens to every session and 591 once invoked, about $0.0001 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 commands, from other repositories
changelog
Generate a "what's new" changelog from merged commits over a time range (e.g. since Monday, last 5 days). Writes user-focused markdown to tmp/.
release
Prepare, cut, and verify a warren release — tracker audits, version bump, CHANGELOG curation, ROADMAP update, push, then watch the pipeline through to published artifacts.
release
Cut a release — bump all workspace versions in sync, generate/update CHANGELOG.md from Conventional Commits, commit and tag (push gated on confirmation).
lavra-ship
Fully automated ship sequence from code-ready to PR-open with beads closed and knowledge captured.
changelog
Create engaging changelogs for recent merges to main branch.
release
Release a new version. Bumps version, updates docs/site/changelog, tags, pushes, and updates the marketplace repo.