A command that pauses a workflow loop by creating a marker that tells it to stop at its next safe point. Work already completed by a worker remains on disk, while some review work is discarded and later restarted.

It is for pausing work on a named specification while a running driver finishes its current action and waits.

It lets a person stop an active workflow without allowing its next mutating action to proceed. The command also records why the pause happened.

How Black-coffe/vulyk configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to Black-coffe/vulyk. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/Black-coffe/vulyk/main/.claude/commands/vulyk-pause.md

Clone the repo

git clone --depth 1 https://github.com/Black-coffe/vulyk

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/black-coffe/vulyk/vulyk-pause/github.svg)](https://agentmods.dev/commands/black-coffe/vulyk/vulyk-pause)

Your own site

<a href="https://agentmods.dev/commands/black-coffe/vulyk/vulyk-pause"><img src="https://agentmods.dev/badge/commands/black-coffe/vulyk/vulyk-pause/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/black-coffe/vulyk/vulyk-pause"><img src="https://agentmods.dev/badge/commands/black-coffe/vulyk/vulyk-pause.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 22 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 323 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00022	$0.00323
Opus 5.5	$0.00009	$0.00129
Sonnet 5.5	$0.00004	$0.00065
Haiku 4.5	$0.00002	$0.00032

Measured 13d ago against content hash 60d1741084d3, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

vulyk-pause 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 13d 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.

.claude/commands/vulyk-pause.md · 20 lines

What it actually says

Pause: "$ARGUMENTS" (the first token is the spec slug; anything after it is the reason).

bash scripts/cycle.sh pause docs/specs/<slug> "<why>" (without a reason it records "no reason given"). Print exactly what it prints: the cycle: <slug> - paused: <why> line and its JSON.
Tell the owner what this does to a loop already running. Every mutating cycle.sh verb checks PAUSE first and exits 3 without acting, so:
- the Workflow driver stops at its next advance; the agent in flight finishes first, and the driver then releases its DRIVER claim itself (pause never removes it);
- a solo or agent loop in a session stops at its next cycle.sh call;
- a worker's edits are already on disk; only its close-story waits for /vulyk-resume;
- a seat or reviewer report in flight is not recorded while paused; after /vulyk-resume the loop dispatches that seat again.
Say plainly: the working tree of vulyk/<slug> is now the owner's to edit, inspect and commit on; nothing in the hive touches it again until /vulyk-resume <slug> clears the semaphore.

Changes

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.

13d ago Changed · +1 lines 60d1741084d3
1mo ago Changed · -6 lines c4d1b3bbb10b
1mo ago First seen · 25 lines · 22 tokens per session scan A 9f525955940d

Subscribe to this mod's changes

vulyk-pause is a command published in the GitHub repository Black-coffe/vulyk (2 stars, last pushed today), licensed MIT. It adds 22 tokens to every session and 323 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-09-14.

Claude Code Project management agentic-coding ai-agents ai-framework anthropic claude

vulyk: Command for Claude Code

Borrowing it

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other commands, from other repositories

flow

jira-breakdown

jira

setup

postmortem

triage