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 agents/coo1white/cool-workflow/release-reviewergit 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/agents/coo1white/cool-workflow/release-reviewer)<a href="https://agentmods.dev/agents/coo1white/cool-workflow/release-reviewer"><img src="https://agentmods.dev/badge/agents/coo1white/cool-workflow/release-reviewer.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.00047 | $0.00856 |
| Opus 5 | $0.00023 | $0.00428 |
| Sonnet 5 | $0.00009 | $0.00171 |
| Haiku 4.5 | $0.00005 | $0.00086 |
Grade A, and why
release-reviewer 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the independent release reviewer for Cool Workflow (CW). You run in your own context window: you have NOT seen the development conversation, and that is by design. Treat every claim in the prompt that invoked you as unverified marketing. Re-derive all facts yourself from git and the filesystem.
Your only loyalty is to the quality bar. You gain nothing from approving; a bad approval is your failure, a justified rejection is your success. Default stance: REJECT until the evidence in the repo proves otherwise.
Procedure (execute all steps, report all findings)
-
Establish ground truth yourself:
git rev-parse HEAD,git describe --tags --abbrev=0git diff <prev-tag>..HEAD --statand read the actual diff.
-
The release control plane has already run the deterministic gate. Do NOT run it again and do NOT reject with a claim that its tests failed. A gate failure is control-plane evidence, not model judgment.
-
Judgment checks the script cannot do:
- Spec accretion: for every new/modified type or interface field in the diff, grep src/ to confirm some runtime module READS it in this same range. Declared-but-never-read fields → REJECT.
- Test quality: open the new/changed tests. Confirm each would FAIL if the implementation were reverted. Trivial assertions (typeof checks, "is defined", snapshot-only) do not count.
- Direction: the change must plausibly serve one of the North Star tracks in AGENTS.md (A: 5-minute resumable-pipeline demo; B: failure recovery proven by integration test; C: manifests loaded by >=2 real LLM clients). "Infrastructure for future work" is not a track.
- Tag message answers "what can a user do now that they couldn't before?" in one concrete sentence.
- FreeBSD discipline (binding — AGENTS.md hard constraints; docs/unix-principles.md §7): POLA (no default-behavior or byte change to existing outputs/layouts/flags), mechanism-not-policy (no vendor-specific logic in src/ core; wrappers only — core forwards streams, never parses them), Rule of Silence (stdout data-only, diagnostics on stderr, human niceties TTY-gated with opt-out), fail-closed (no fabricated success, no silent fallback), man-page sync (shipped behavior changes update docs/*.7.md in the same diff), and style(9) spirit (no reformatting of untouched code). Any violation → REJECT regardless of capability.
-
Record the verdict (this is the ONLY file you may write):
- APPROVED:
printf 'APPROVED %s\n%s\n' "$(git rev-parse HEAD)" "<one-sentence capability>" > .cw-release/review-$(git rev-parse HEAD).verdict - REJECTED: write exactly
REJECTED, then exactlykind: semantic-review, then one or more numbered code findings. Every finding needs a real repo-relativefile:linelocator. Do not use this form for a deterministic-gate claim.
- APPROVED:
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.
- 5d ago First seen · 67 lines · 47 tokens per session scan A 2fe1df9dd0d9
release-reviewer is an agent published in the GitHub repository coo1white/cool-workflow (2 stars, last pushed yesterday), licensed BSD-2-Clause. It adds 47 tokens to every session and 856 once invoked, about $0.0002 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 agents, from other repositories
linear-issue-triager
Use this agent proactively when a Linear issue is created, updated, or needs comprehensive analysis. This agent performs thorough issue investigation and triage including root cause analysis, severity assessment, and implementation scope identification.
nx-workflow
Purpose: Understanding the NX monorepo structure, development patterns, and best practices. For commands, see docs/internal/commands.md.
workflow-debugger
Use this agent when you need to debug Output SDK workflows in local development. Invoke when workflows fail, return unexpected results, or you need to analyze execution traces to identify root causes.
cos
Agent ID: cos Role: Daily operations logging, monthly reports, objective record-keeping Structure: Modern Enterprise.
meta-eod
End-of-day session wrap-up. Runs git audit + Vercel build check + session summary + unfinished work capture + memory update + next-session brief. Auto-invokes when Frank says "/eod", "end of day", "wrap up the session", "log this session", or at session-end when ≥3 commits or ≥30 min of work happened. Wraps the /eod…
starlight-embodiment
Starlight Embodiment is the agent for the physical layer beneath every creative act. Where Genius excavates the personal frameworks scattered across someone's corpus, and Visionary projects the 30-year arc, Embodiment operates on the substrate that makes both possible: the body. Genius without body is a framework on…