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 skills/coo1white/cool-workflow/deploy-checknpx skills add coo1white/cool-workflow --skill deploy-checkgit 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/skills/coo1white/cool-workflow/deploy-check)<a href="https://agentmods.dev/skills/coo1white/cool-workflow/deploy-check"><img src="https://agentmods.dev/badge/skills/coo1white/cool-workflow/deploy-check.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.00054 | $0.00321 |
| Opus 5 | $0.00027 | $0.00161 |
| Sonnet 5 | $0.00011 | $0.00064 |
| Haiku 4.5 | $0.00005 | $0.00032 |
Grade A, and why
deploy-check 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 3d 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
Deploy Check
Overview
Deploy check is the verifier side of release work. It confirms the artifact a user receives matches the source, docs, manifests, and stated capability.
Workflow
- Confirm the intended capability and release scope.
- Inspect branch status and generated artifact drift.
- Run the deterministic gates.
- Check docs/man-page coverage for shipped behavior.
- Check package contents and
dist/policy. - Report risk before any tag or publish step.
Commands
npm run build
npm test
npm run gen:manifests -- --check
npm run index:check
npm run version:sync
npm run release:check
git diff --check
For package inspection:
npm pack --dry-run
Red Lines
- Do not tag without test evidence.
- Do not write reviewer verdict files by hand.
- Do not silently skip
dist/drift if the package still shipsdist/. - Do not publish undocumented behavior.
- Do not call a release ready if generated manifests or project index drift.
Output Rules
Return a ship/no-ship verdict, gate results, artifact risks, and the next operator action.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 56 lines · 54 tokens per session scan A ce5d1adab5a8
deploy-check is a skill published in the GitHub repository coo1white/cool-workflow (2 stars, last pushed today), licensed BSD-2-Clause. It adds 54 tokens to every session and 321 once invoked, about $0.0003 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 skills, from other repositories
agent-workflow-playbook
AI Agent Workflow & Skill Architecture Guide — turn expert work into measurable, reusable agent systems. Covers workflow discovery, skill decomposition, harness design, evaluation, human escalation, observability, cost control, and multi-agent orchestration. Includes a measured marketing-delivery case: 15 people × 3–4…
aperture_lab_autoresearch
Run Aperture Lab F-Stop on imported public trajectories, prepare review artifacts, compare disagreements, and propose bounded semantic-layer improvements under strict replay gates.
aperture_lab_reviewer
Review Aperture Lab F-Stop offline review prompts and return JSON-only findings about title, summary, status, intentFrame, toolFamily, and consequence. Use when acting as the reviewer model inside the Aperture Lab F-Stop loop; do not edit code and do not return prose outside the required JSON.
wakeflow-controller
Use when Wakeflow total control starts or resumes Wakeflow Delivery Loop in Claude Code, reviews strict TargetResult records, prepares typed delivery transport, coordinates the v3 Claude host adapter, decides acceptance / rework / block / next wave, or stops unattended automation.
wakeflow-target
Use when a target Claude Code window receives an exact Wakeflow v3 delivery, executes only its assigned TaskPackage, records a transport-bound TargetResult, or performs an authorized Controller return without taking controller authority.
progressive-chain-validation
Use when the Test window needs a source-derived chain plan, node-by-node validation, isolated repair evidence, scoped round verdicts, before/after metrics, or a progressive validation plan for a long workflow.