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.
git clone --depth 1 https://github.com/coo1white/cool-workflowWrote 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)<a href="https://agentmods.dev/commands/coo1white/cool-workflow/release"><img src="https://agentmods.dev/badge/commands/coo1white/cool-workflow/release/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"><img src="https://agentmods.dev/badge/commands/coo1white/cool-workflow/release.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.00027 | $0.00408 |
| Opus 5.5 | $0.00011 | $0.00163 |
| Sonnet 5.5 | $0.00005 | $0.00082 |
| Haiku 4.5 | $0.00003 | $0.00041 |
Grade A, and why
release 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 today.
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
A release is TWO steps (see AGENTS.md's "Shipping a release" section). This
command does ONLY step 1, the agent-prep half. Step 2 — running the gate,
the independent reviewer, signing the verdict, creating the tag, and
publishing — is the OPERATOR's own command, npm run release -- X.Y.Z, run
in their own terminal where CW_RELEASE_VERDICT_PRIVKEY is set. Never run
release-oneclick.mjs or release-flow.mjs --cut, and never create a tag by
hand — those steps need the signing key, which an agent must never read or
hold.
Both npm run commands below run with cwd plugins/cool-workflow/ (no
root package.json).
Steps, in order — stop at the first failure:
-
Ask the user (if not already given) for the target version
X.Y.Zand a one-sentence description of the capability this release adds. -
Run
npm run bump:version -- X.Y.Z --contentto stamp every version surface and auto-fill content placeholders (docs, README). -
Run
npm run sync:project-index -- --repo-onlyto regenerate the project index. -
Run a full clean rebuild (
npm run build) and confirm it is clean. -
Commit the changes and open the version-bump PR onto
main(branch name should describe the release, e.g.release/X.Y.Z).
Report: the PR link, the version, and the capability sentence. Then tell
the user the PR needs to merge before they run npm run release -- X.Y.Z
themselves to cut, sign, and publish the release — do not attempt that
step in this session.
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.
- today Changed 5fc24748ff94
- 1mo ago First seen · 37 lines · 27 tokens per session scan A a38f8e6b9e59
release is a command published in the GitHub repository coo1white/cool-workflow (2 stars, last pushed today), licensed BSD-2-Clause. It adds 27 tokens to every session and 408 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
fix-issues
Diagnose, reproduce, then fix reproducible open GitHub issues in parallel: one clean worktree/issue; symlink build artifacts to avoid rebuilds.
review-prs
Parallel PR triage: decide merge-worthiness, prepare rebased worktrees, fix blockers, return them for human merge.
release
Release all packages at specified version.
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.
acos-checkpoint
Create checkpoints before risky operations. Rollback if things go wrong.
pod
Create a Wakeflow pod for parallel work, or close one after its branch has been merged or abandoned.