vulyk: Command for Claude Code

.claude/commands/vulyk-status.md

vulyk-status is a command for Claude Code from Black-coffe/vulyk. It costs 29 tokens per session (1,253 once invoked), scanned A, original, MIT.

A command that creates a status report for a Hive dashboard, covering work stories, memory freshness, learnings, skill usage, and model-budget settings. The report reads project metadata and related files.

In plain words
What is it for?
Use it to check story progress, find outdated memory notes, count unsorted learnings, review skill statistics, and assess when to hand work off.
Why use it?
It brings several project-health checks into one report and points out stale or unclear information.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: reads .claude/ paths; positional $N argument.

This is Black-coffe/vulyk's own configuration. It tells Claude Code how to work on vulyk itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything vulyk configures →

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

agentmods badge for vulyk-status

README.md
[![agentmods](https://agentmods.dev/badge/commands/black-coffe/vulyk/vulyk-status/github.svg)](https://agentmods.dev/commands/black-coffe/vulyk/vulyk-status)
Your own site
<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.

agentmods 80×15 button for vulyk-status

Your own site · 80×15
<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>
Per session 29 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,253 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.

ModelPer sessionOnce 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

Measured today against content hash 2d8c1ba0dad1, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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.

.claude/commands/vulyk-status.md · 60 lines

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.

  1. Driver and release. Print driver: workflow if Workflow is in your own tool list this session, else driver: agent loop (Tier 3-4 run their agents from the Queen's session; Tier 1-2 build solo either way). Then merged locally, not pushed: <n>: resolve the default branch as ship-check.sh does (git symbolic-ref --short refs/remotes/origin/HEAD, else main/master), then git log origin/<default>..<default> --oneline | wc -l; print no remote when origin is absent.
  2. Council. If memory/stats/council.jsonl does not exist, print council: no rounds yet and skip the rest of this step. Otherwise one awk pass over it, printed as-is:
    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.jsonl
    
    Escaped defects: grep -rl '^\*\*Escaped from:\*\*' docs/specs/*/brief.md, counting a match only when memory/stats/council.jsonl holds a GREEN row for the slug it names (grep -F "\"spec\":\"<slug>\"" memory/stats/council.jsonl | grep -q '"verdict":"GREEN"'). Print council: <specs> specs · median <n> rounds to green · <n> escalations · <n> escaped defects.
  3. Defects. If docs/defects/ holds no card, print defects: no library; otherwise print defects: followed by the output of bash scripts/defects-index.sh --counts.
  4. 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. The totalTokens a Workflow run prints is a sum of final contexts, not spend; quote this report instead.
  5. Stories. Run bash scripts/state.sh and read .claude/state.json into a table: spec, stage, story, status, tier. stage is the cycle confirmation reached (docs/cycle.md); study marks a document deliverable; a spec with a council round shows 04-council:<verdict>; a PAUSE file shows paused. The view is derived: a story file that disagrees wins. Statuses are todo | done | blocked; older specs may still carry in-progress. Report unrecognised counts out loud.
  6. Memory freshness. memory/map/* last-verified dates against recent git churn in their modules (git log --since per path); flag stale ones, and a .stale flag left by scripts/git-hooks/post-merge.
  7. Maintenance. Print the brief's due lines: echo '{}' | bash .claude/hooks/session-start-brief.sh | grep -E 'maintenance due|waits for', else maintenance: nothing due.
  8. Skill usage. Top and bottom entries of memory/stats/skills.json; name the candidates the next /vulyk-evolve will examine.
  9. 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 to opus. On a long session, recommend /vulyk-handoff, then /clear.
  10. Context hygiene, only on a fresh session: suggest /context to see what the session starts with, and /mcp to switch off servers this project never calls.

Format: compact tables, no padding. End with the single most useful next action.

Read the full file on GitHub · 60 lines

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.

  1. today Changed 2d8c1ba0dad1
  2. 10d ago Changed · +2 lines af1974eb3da9
  3. 14d ago Changed dcc8c61a2327
  4. 1mo ago Changed · +20 lines · +4 tokens per session d7fa6ddcd333
  5. 1mo ago Changed 556a23515973
  6. 1mo ago Changed · +22 lines · +11 tokens per session 405eec919baa
  7. 1mo ago Changed 2b3c36ba4fbf
  8. 1mo ago Changed c05b58209077
  9. 2mo ago First seen · 16 lines · 14 tokens per session scan A bd4e02f18d80

Subscribe to this mod's changes

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.