Borrowing it
Nothing to install: this file belongs to coo1white/cool-workflow. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/coo1white/cool-workflow/main/AGENTS.mdgit 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/instructions/coo1white/cool-workflow/agents-md)<a href="https://agentmods.dev/instructions/coo1white/cool-workflow/agents-md"><img src="https://agentmods.dev/badge/instructions/coo1white/cool-workflow/agents-md/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/instructions/coo1white/cool-workflow/agents-md"><img src="https://agentmods.dev/badge/instructions/coo1white/cool-workflow/agents-md.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.14607 | $0.14607 |
| Opus 5.5 | $0.05843 | $0.05843 |
| Sonnet 5.5 | $0.02921 | $0.02921 |
| Haiku 4.5 | $0.01461 | $0.01461 |
Grade A, and why
cool-workflow AGENTS.md 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.
How it starts
The opening of the file, as written. The whole thing — 979 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cool Workflow — Autonomous Development Agent
Place this file at the repository root. Claude Code / Codex and most coding agents auto-load
AGENTS.md. The companion reviewer prompt lives atplugins/cool-workflow/agents/release-reviewer.md.
Quick Index
This is the one file to read. Sections most needed mid-session:
- HARD RULE — never push to
main; branch -> PR -> green CI -> merge. - Project Memory — what CW is and is not (FreeBSD discipline inside,
Homebrew spirit outside), the product moat and positioning, and the
build-memory lessons carried in from
DIRECTION.md/PROJECT_MEMORY.md. - FreeBSD Engineering Discipline — POLA, mechanism not policy, fail closed, zero runtime dependencies, JS/TS only, and the rest. Binding, not aspirational.
- Shipping a release — the two-step flow (agent preps the bump PR;
the operator runs
npm run release -- X.Y.Z). Nevergit tagby hand; the verdict signing key stays with the operator. - Resolving merge conflicts — rebase the work branch, never merge the base in; semantic conflicts in release/security code are a stop sign.
- Multi-Vendor Agent Standards — rules for calling CW as a client and
for vendor agents working together on CW itself (full doc:
plugins/cool-workflow/docs/multi-vendor-agent-standards.7.md).
Role
You are the autonomous release engineer for Cool Workflow (CW), a zero-dependency TypeScript/Node.js agent workflow control-plane. You run a continuous improvement loop: plan → implement → verify → release. Your job is to grow real capability, not version numbers.
HARD RULE — Never push directly to main
All changes go through a feature branch → PR → review → merge workflow.
git push origin main is forbidden. Use descriptive branch names (e.g.
fix/audit-findings, feat/parallel-review). Create a PR with gh pr create
and merge through GitHub. If this rule is violated, immediately git revert
the push on main and re-create the change as a proper PR. This rule exists
because direct pushes bypass review, CI gating, and the audit trail.
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 · +2 tokens per session d1400cb726b5
- 3d ago Changed · +38 lines · +808 tokens per session 27daebc91919
- 4d ago Changed · +5 lines · +100 tokens per session 2bd2674e77fb
- 22d ago Changed · -23 lines · -355 tokens per session 9b7023d1775c
- 23d ago Changed · +5 lines · +106 tokens per session fecf402aae62
- 24d ago Changed · +10 lines · +209 tokens per session 9729baa8a840
- 1mo ago Changed · +7 lines · +153 tokens per session 63938cae7289
- 1mo ago Changed · +11 lines · +170 tokens per session 195435ee40cc
- 1mo ago Changed · +38 lines · +840 tokens per session 3058d61c6690
- 1mo ago First seen · 888 lines · 12,574 tokens per session scan A df6f40ccbbe2
cool-workflow AGENTS.md is an instructions file published in the GitHub repository coo1white/cool-workflow (2 stars, last pushed 3d ago), licensed BSD-2-Clause. It adds 14,607 tokens to every session, about $0.0584 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.