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.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.1 | $0.00014 | $0.00460 |
| Opus 5 | $0.00007 | $0.00230 |
| Sonnet 5 | $0.00003 | $0.00092 |
| Haiku 4.5 | $0.00001 | $0.00046 |
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.
What it actually says
Produce the hive status report. Read only metadata - this command must stay cheap:
- Stories: run
bash scripts/state.shand read.claude/state.json-> table: spec, itsstage(which confirmation of the six-stage cycle it has reached -docs/cycle.md), story, status, assigned tier. It is a derived view, regenerated on the spot, never a source of truth - if a number here disagrees with a story file, the story file wins and the view was stale. Reportunrecognisedcounts out loud rather than folding them into anything: a spec written before thetodo|in-progress|done|blockedconvention is not a spec with nothing done, and treating it as one is the derived view lying. - Memory freshness:
memory/map/*last-verified dates vs. recent git churn in their modules (git log --sinceper path); flag stale. Note ifscripts/git-hooks/post-mergeleft a.staleflag. - Learnings buffer: count raw files in
memory/learnings/awaiting consolidation; remind about /vulyk-gc past 10. - Skill usage: top/bottom entries from
memory/stats/skills.json; note candidates the next /vulyk-evolve will examine. - Budget posture: run
bash scripts/top-model.sh --explainand show it - the resolved top model, the plan it was read from, the Tier 4 pairing, and whether the Queen's own session is pinned to it; then the routing matrix one-liner. If the session has been long, recommend/vulyk-handoffthen/clearafter this report. - Context hygiene (only when the session is fresh — otherwise the advice arrives too late to act on): suggest
/contextto see what the session starts with, and/mcpto switch off servers this project never calls. Skip this step entirely on a long session.
Format: compact tables, no prose 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 2b3c36ba4fbf
- 2d ago Changed c05b58209077
- 7d 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 2d ago), licensed MIT. It adds 14 tokens to every session and 460 once invoked, about $0.0001 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 commands, from other repositories
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.
add-todo
Capture idea or task as todo from current conversation context.
note
Zero-friction idea capture. Append, list, or promote notes to todos.
resume-work
Resume work from previous session with full context restoration.