vulyk: Command for Claude Code

.claude/commands/vulyk-evolve.md

vulyk-evolve is a command for Claude Code from Black-coffe/vulyk. It costs 33 tokens per session (3,769 once invoked), scanned A, original, MIT.

A weekly review command for finding repeated problems in an agent setup and proposing configuration, rule, prompt, or skill changes as a reviewable set of edits.

In plain words
What is it for?
Use it to identify friction, find unused skills to retire, suggest new reusable rules, and prepare a dated changeset with reasons and rollback notes.
Why use it?
It turns scattered learning notes and usage data into evidence-based maintenance suggestions, while leaving a person in control of what gets applied.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: reads .claude/ paths; mentions CLAUDE.md; 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 →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is X="$(mktemp)"; bash .claude/hooks/defect-intake.sh --lexicon > "$X"; L=""; OUT=""; seen=0.

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

README.md
[![agentmods](https://agentmods.dev/badge/commands/black-coffe/vulyk/vulyk-evolve/github.svg)](https://agentmods.dev/commands/black-coffe/vulyk/vulyk-evolve)
Your own site
<a href="https://agentmods.dev/commands/black-coffe/vulyk/vulyk-evolve"><img src="https://agentmods.dev/badge/commands/black-coffe/vulyk/vulyk-evolve/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-evolve

Your own site · 80×15
<a href="https://agentmods.dev/commands/black-coffe/vulyk/vulyk-evolve"><img src="https://agentmods.dev/badge/commands/black-coffe/vulyk/vulyk-evolve.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 33 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,769 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.00033 $0.03769
Opus 5.5 $0.00013 $0.01508
Sonnet 5.5 $0.00007 $0.00754
Haiku 4.5 $0.00003 $0.00377

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

Security

Grade A, and why

vulyk-evolve 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-evolve.md · 94 lines

How it starts

The opening of the file, as written. The whole thing — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Run the evolution cycle. Use the insight-harvester and skill-gardener skills - they define the method. "$ARGUMENTS"

Nobody has to remember this command: the SessionStart brief says maintenance due: ... evolve (...) when it never ran, or ran 7+ days ago with a council round since, and the Queen runs it after the owner's task, on the default branch with a clean tree.

  1. Ledger (memory/stats/evolve.jsonl, owned by scripts/evolve-ledger.py). Run bash scripts/py.sh scripts/evolve-ledger.py . resolve - it records the owner's verdict on earlier changesets from git (merged = accepted, branch deleted unmerged = rejected; add --reason-for <branch>=<text> when the owner gave one) - then bash scripts/py.sh scripts/evolve-ledger.py . window and read it before anything else. A hypothesis it shows rejected is not proposed again unless this run's evidence is newer than the rejection. If bash scripts/py.sh scripts/evolve-ledger.py . pending names a branch, stop: tell the owner in one line that <branch> waits for review (merge to accept, delete the branch to reject) and propose nothing new.

  2. Harvest. Read memory/learnings/ (raw + CONSOLIDATED), memory/stats/skills.json, and - if the user can paste it - the output of the built-in /insights command (ask once; proceed without it if unavailable). Then the week's spend: bash scripts/py.sh scripts/token-report.py . --since "$(date -u -d '-7 days' +%Y-%m-%d 2>/dev/null || date -u -v-7d +%Y-%m-%d)", printed as-is - one line per spec with raw and weighted tokens, dispatches and rounds. That report is the spend; the totalTokens a Workflow run prints is a sum of final contexts and never counts as spend. A spec whose dispatches or rounds stand out is evidence for step 3's friction list. Then the owner's corrections of the week and how many reached docs/defects/. The lexicon is the intake hook's own (--lexicon), and the reader is litopys 0.4.0+ corrections. Run the block as written. It prints one line and blocks nothing:

    X="$(mktemp)"; bash .claude/hooks/defect-intake.sh --lexicon > "$X"; L=""; OUT=""; seen=0
    while IFS= read -r c; do   # PATH's copy first, then cached copies newest first: the first with the verb wins
      [ -f "$c" ] || continue; seen=1
      if OUT="$(bash "$c" corrections --since "$(date -u -d '-7 days' +%Y-%m-%d 2>/dev/null || date -u -v-7d +%Y-%m-%d)" --lexicon "$X" 2>/dev/null)"; then L="$c"; break; fi
    done < <(command -v litopys; ls -d "$HOME"/.claude/plugins/cache/litopys/litopys/*/bin/litopys 2>/dev/null | sort -rV)
    if [ -n "$L" ]; then   # a quote opening with ">" is a relayed side-agent note: model text, not the owner's
      r=$(printf '%s\n' "$OUT" | grep -c ' · «> '); OUT="$(printf '%s\n' "$OUT" | grep -v ' · «> ')"
      n=$(printf '%s\n' "$OUT" | grep -c ' · lexicon · '); m=$(printf '%s\n' "$OUT" | grep -c ' · record · '); u=0
      while IFS= read -r l; do q="${l#*«}"; q="${q%»}"; grep -rqF -- "$q" docs/defects 2>/dev/null || u=$((u+1)); done \
        < <(printf '%s\n' "$OUT" | grep -E ' · (lexicon|record) · ')
      echo "corrections (7d): $n by lexicon · $m in records · $u not in docs/defects · $r relayed notes left out"
    elif [ "$seen" = 1 ]; then echo "corrections: no installed litopys has the corrections verb - update it to 0.4.0+"
    else echo "corrections: litopys not installed - no count"; fi
    rm -f "$X"
    

    A line counts as filed when docs/defects/ holds it verbatim. The lexicon also catches remarks that are not corrections, so treat the three numbers as a lead with its n, never as a rate on their own. A remark that is not filed is evidence for step 3: file its quote into the matching card (Law 6), not a new rule in prose.

  3. Council check-in (read-only; nothing here writes anything). If memory/stats/council.jsonl does not exist, print council: no rounds yet and skip to step 3. Otherwise run the same awk pass /vulyk-status step 2 uses, restricted to the last 7 days:

    SINCE="$(date -u -d '-7 days' +%Y-%m-%dT%H:%M:%SZ 2>/dev/null || date -u -v-7d +%Y-%m-%dT%H:%M:%SZ)"
    awk -v since="$SINCE" '
      { match($0, /"ts":"[^"]*"/);      ts=substr($0, RSTART+6, RLENGTH-7) }
      ts < since { next }
      { 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
    

    plus the same escaped-defect grep as /vulyk-status step 2, restricted to briefs whose file mtime falls in the last 7 days (date -r <brief.md> +%s vs. date -u -d '-7 days' +%s 2>/dev/null || date -u -v-7d +%s). Print council (7d): <specs> specs · median <n> rounds to green · <n> escalations · <n> escaped defects. Then the comparison the grill names - human.jsonl rows with "verdict":"REJECTED" in the same window:

    awk -v since="$SINCE" '
      { match($0, /"ts":"[^"]*"/); ts=substr($0, RSTART+6, RLENGTH-7) }
      ts < since { next }
      $0 ~ /"verdict":"REJECTED"/ { c++ }
      END { print c+0 }
    ' memory/stats/human.jsonl
    

    Print human.jsonl REJECTED (7d): <n>. Every number in this step is printed with its n, and none of them proves a trend on its own: a week holds a handful of specs, so a count of 0-2 against 0-2 is noise (report rrsi-self-improvement §1). Nothing in this step applies anything; it feeds step 3's diagnosis the way skills.json already does.

Read the full file on GitHub · 94 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 ed05605160cd
  2. 2d ago Changed · +2 lines 9b6cdd4597e2
  3. 1mo ago Changed · +30 lines 03c68ddcae09
  4. 1mo ago Changed · +1 lines · +3 tokens per session 46ac097d8ac4
  5. 1mo ago Changed · +14 lines 4e66ca485067
  6. 1mo ago Changed · +33 lines · +7 tokens per session 6876d4daf3e6
  7. 2mo ago First seen · 14 lines · 23 tokens per session scan A dbed3e71ca41

Subscribe to this mod's changes

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