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-status.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-status)<a href="https://agentmods.dev/commands/black-coffe/vulyk/vulyk-status"><img src="https://agentmods.dev/badge/commands/black-coffe/vulyk/vulyk-status/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-status"><img src="https://agentmods.dev/badge/commands/black-coffe/vulyk/vulyk-status.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.00029 | $0.01253 |
| Opus 5.5 | $0.00012 | $0.00501 |
| Sonnet 5.5 | $0.00006 | $0.00251 |
| Haiku 4.5 | $0.00003 | $0.00125 |
Grade A, and why
vulyk-status 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.
How it starts
The opening of the file, as written. The whole thing — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Produce the hive status report. Read only metadata; this command stays cheap.
- Driver and release. Print
driver: workflowifWorkflowis in your own tool list this session, elsedriver: agent loop(Tier 3-4 run their agents from the Queen's session; Tier 1-2 build solo either way). Thenmerged locally, not pushed: <n>: resolve the default branch asship-check.shdoes (git symbolic-ref --short refs/remotes/origin/HEAD, elsemain/master), thengit log origin/<default>..<default> --oneline | wc -l; printno remotewhenoriginis absent. - Council. If
memory/stats/council.jsonldoes not exist, printcouncil: no rounds yetand skip the rest of this step. Otherwise oneawkpass over it, printed as-is:
Escaped defects:awk ' { match($0, /"spec":"[^"]*"/); spec=substr($0, RSTART+8, RLENGTH-9) } { match($0, /"round":[0-9]+/); round=substr($0, RSTART+8, RLENGTH-8) } { match($0, /"verdict":"[^"]*"/); verdict=substr($0, RSTART+11, RLENGTH-12) } { specs[spec]=1 if (verdict=="GREEN" && (!(spec in firstgreen) || round+0 < firstgreen[spec]+0)) firstgreen[spec]=round if (verdict=="ESCALATE") escalations++ } END { n=0; for (s in specs) n++ g=0; for (s in firstgreen) { g++; rounds[g]=firstgreen[s]+0 } for (i=1;i<=g;i++) for (j=i+1;j<=g;j++) if (rounds[j]<rounds[i]) { t=rounds[i]; rounds[i]=rounds[j]; rounds[j]=t } med=0; if (g>0) { if (g%2==1) med=rounds[(g+1)/2]; else med=(rounds[g/2]+rounds[g/2+1])/2 } printf "specs:%d median:%s escalations:%d\n", n, med, escalations+0 } ' memory/stats/council.jsonlgrep -rl '^\*\*Escaped from:\*\*' docs/specs/*/brief.md, counting a match only whenmemory/stats/council.jsonlholds aGREENrow for the slug it names (grep -F "\"spec\":\"<slug>\"" memory/stats/council.jsonl | grep -q '"verdict":"GREEN"'). Printcouncil: <specs> specs · median <n> rounds to green · <n> escalations · <n> escaped defects. - Defects. If
docs/defects/holds no card, printdefects: no library; otherwise printdefects:followed by the output ofbash scripts/defects-index.sh --counts. - Token spend.
bash scripts/py.sh scripts/token-report.py . --since "$(date -u -d '-14 days' +%Y-%m-%d 2>/dev/null || date -u -v-14d +%Y-%m-%d)"and print its per-spec lines as-is: raw and weighted tokens, dispatches, rounds. ThetotalTokensa Workflow run prints is a sum of final contexts, not spend; quote this report instead. - Stories. Run
bash scripts/state.shand read.claude/state.jsoninto a table: spec,stage, story, status, tier.stageis the cycle confirmation reached (docs/cycle.md);studymarks a document deliverable; a spec with a council round shows04-council:<verdict>; aPAUSEfile showspaused. The view is derived: a story file that disagrees wins. Statuses aretodo | done | blocked; older specs may still carryin-progress. Reportunrecognisedcounts out loud. - Memory freshness.
memory/map/*last-verifieddates against recent git churn in their modules (git log --sinceper path); flag stale ones, and a.staleflag left byscripts/git-hooks/post-merge. - Maintenance. Print the brief's due lines:
echo '{}' | bash .claude/hooks/session-start-brief.sh | grep -E 'maintenance due|waits for', elsemaintenance: nothing due. - Skill usage. Top and bottom entries of
memory/stats/skills.json; name the candidates the next/vulyk-evolvewill examine. - Budget posture. Show
bash scripts/top-model.sh --explain: the gate model, the plan it came from, the Tier 4 pairing, and whether the Queen's session is pinned toopus. On a long session, recommend/vulyk-handoff, then/clear. - Context hygiene, only on a fresh session: suggest
/contextto see what the session starts with, and/mcpto switch off servers this project never calls.
Format: compact tables, no padding. End with the single most useful next action.
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 2d8c1ba0dad1
- 10d ago Changed · +2 lines af1974eb3da9
- 14d ago Changed dcc8c61a2327
- 1mo ago Changed · +20 lines · +4 tokens per session d7fa6ddcd333
- 1mo ago Changed 556a23515973
- 1mo ago Changed · +22 lines · +11 tokens per session 405eec919baa
- 1mo ago Changed 2b3c36ba4fbf
- 1mo ago Changed c05b58209077
- 2mo ago First seen · 16 lines · 14 tokens per session scan A bd4e02f18d80
vulyk-status is a command published in the GitHub repository Black-coffe/vulyk (2 stars, last pushed today), licensed MIT. It adds 29 tokens to every session and 1,253 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
park
Park current session for later resume (append to Markdown file).
resume
Resume an interrupted multi-phase orc command from its last checkpoint. Reads .orc/orc.json for active sessions, picks one, jumps to the next pending phase. Workspace-aware.
retro
Retrospective on a coding session — proposes changes to the agent's environment (navigation pointers, automated checks, coding standards, steering files, tool economy, information access), most severe first; applies accepted in-repo changes and files the rest through the tracker gate.
iterate
A command that repeatedly selects, completes, checks, and records development tasks within one coding session.
pair
A pair-programming command that makes the developer and coding agent work through a task together. Pair programming means discussing the work, agreeing on decisions, and implementing it step by step with regular confirmation.
checkpoint
A checkpoint workflow that records project progress so work can be resumed after the conversation context is cleared. It combines verification, a Git commit, progress notes, and saved session information.