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.
curl -O https://raw.githubusercontent.com/Black-coffe/vulyk/main/.claude/commands/vulyk-review.mdgit clone --depth 1 https://github.com/Black-coffe/vulykWrote 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/black-coffe/vulyk/vulyk-review)<a href="https://agentmods.dev/commands/black-coffe/vulyk/vulyk-review"><img src="https://agentmods.dev/badge/commands/black-coffe/vulyk/vulyk-review/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/black-coffe/vulyk/vulyk-review"><img src="https://agentmods.dev/badge/commands/black-coffe/vulyk/vulyk-review.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.00023 | $0.01141 |
| Opus 5.5 | $0.00009 | $0.00456 |
| Sonnet 5.5 | $0.00005 | $0.00228 |
| Haiku 4.5 | $0.00002 | $0.00114 |
Grade A, and why
vulyk-review 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
Run one council round on: "$ARGUMENTS" (default: the spec whose **Branch:** matches the current
branch). Every call below that runs advance carries timeout: 600000.
- Claim and advance.
stamp="$(openssl rand -hex 8 2>/dev/null || bash scripts/py.sh -c 'import secrets; print(secrets.token_hex(8))')", thenbash scripts/cycle.sh advance docs/specs/<slug> --stamp $stamp --claim.ok:falsewithheld by: another driver holds the spec; print itserrorand stop. Otherwise act onnext:dispatch:<seats>: go to step 2.green: the newest round is green and current. If the owner still wants a round, runbash scripts/cycle.sh open-round docs/specs/<slug> --commit --stamp $stamp(the tier's ceiling still counts it; exit 6 means it is reached), thenadvance --stamp $stampagain.build:<W>: stories are open, or the last round was RED andadvancehas cut the repair story. Release and point at/vulyk-build.escalated,paused,shipped,briefed, or anyok:false: release and report it as/vulyk-build's Terminal section does.
- Dispatch exactly the seats
nextnames, in one message, as/vulyk-builddescribes: each writes to.vulyk/reports/<slug>/round-<round>/<seat>.attempt-<k>.mdwith k fromstatus.seat_attempt; blind seats get slug, round,courtand the report path only, neverround_dir;lead-reviewgets the spec, branch, head, report path, and from round 2sinceand the previous round's directory, at Tier 1-3 withmodel: <r>fromr="$(bash scripts/model-profile.sh --role review)"only when the profile is notsonnet-builds(else no model parameter), and two reviewers (review-top,review-second) at Tier 4. Blind seats getmodel: <s>froms="$(bash scripts/model-profile.sh --role seat)"only when the profile (bash scripts/model-profile.sh) is notsonnet-builds. A seat whose dispatch returns the Fable-limit refusal (an error carryingYou've reached your Fable limit/model_requires_usage_credits, or a text that starts withAgent terminated early due to an API errorand carriesreached your Fable limit; a report quoting it is a report) and was not already onopusis redispatched once with the same prompt and agent type andmodel: opus; then,<from>the model it was passed (""when none):bash scripts/journal.sh docs/specs/<slug> 04-council "fallback: <agent> round-<round>/<seat> <from> -> opus (Fable limit; ADR-015 exception)" "ingest",bash scripts/telemetry.sh record fable_limit_fallback 1 0 --spec <slug> --ref <slug>:round-<round>/<seat>:<agent> --model fable --agent <agent>, and one sentence to the owner, in the owner's language. A refusal on the redispatch is the existing path: the seat stays absent. No other error is retried this way. - Record and judge:
bash scripts/cycle.sh advance docs/specs/<slug> --stamp $stamp --ingest. A seat still listed innextwas rejected: re-dispatch it once with itsrejectederror appended, then--ingestagain. - Release, whatever happened:
bash scripts/cycle.sh release docs/specs/<slug> $stamp. Print the newest**Council:**line of plan.md and act onnext:green: ask the owner once withAskUserQuestion, in the owner's language: «: council GREEN, round . Выпускаем?», yes first and recommended. Yes: runvulyk-shipwith the Skill tool (args<slug>). No, or noAskUserQuestion(claude -p): recommend/vulyk-shipin one line.build:<W>: the round was RED and the repair story is written; it is built through/vulyk-build, never by hand in this command.escalated: print## Needs a humanfrom plan.md verbatim. The owner chooses:human-check.sh ACCEPTED,cycle.sh reopen "<decision>", or leaving the spec open.
The council's verdict is what this command produces; there is no stop for the owner inside it.
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 81aa2c90e495
- 2d ago Changed · +9 lines 84d211747aea
- 10d ago Changed · +3 lines 5ad367d0816b
- 1mo ago Changed · +2 lines 819427b90d91
- 1mo ago Changed · -55 lines · +5 tokens per session 5240370da8d0
- 1mo ago Changed · +1 lines 650e4a2687ac
- 1mo ago Changed · +75 lines · +4 tokens per session 6d57626a4148
- 1mo ago Changed cab23cee260a
- 1mo ago Changed 5b87394d2c63
- 2mo ago First seen · 17 lines · 14 tokens per session scan A 3393df9115d3
vulyk-review is a command published in the GitHub repository Black-coffe/vulyk (2 stars, last pushed today), licensed MIT. It adds 23 tokens to every session and 1,141 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
audit-agents-skills
Audit quality of agents, skills, and commands in a Claude Code project.
address
Answer reviewer comments on YOUR open PR — categorize unresolved threads, push fixes, and post replies. Workspace-aware across linked PRs.
review
Review the current diff with a fresh-context agent that cannot edit.
analyze
A command that examines a codebase’s Git history and file structure to find coding patterns and team habits, then records them as reusable documentation.
audit
Review past Claude Code sessions for PBR workflow compliance and UX quality.
security-audit
Comprehensive security audit of your project AND Claude Code configuration. Analyzes secrets exposure, injection surfaces, dependencies, hook security, and produces a scored security posture assessment.