Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add commands/black-coffe/vulyk/vulyk-evolvegit 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-evolve)<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="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.00023 | $0.00392 |
| Opus 5 | $0.00012 | $0.00196 |
| Sonnet 5 | $0.00005 | $0.00078 |
| Haiku 4.5 | $0.00002 | $0.00039 |
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 5d ago.
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 the evolution cycle. Use the insight-harvester and skill-gardener skills - they define the method. "$ARGUMENTS"
- Harvest. Read
memory/learnings/(raw + CONSOLIDATED),memory/stats/skills.json, and - if the user can paste it - the output of the built-in/insightscommand (ask once; proceed without it if unavailable). - Diagnose. Produce three lists with evidence: (a) top 3 friction patterns (repeated mistakes, expensive habits, recurring re-explanations); (b) skills/rules unused for 3+ weeks -> archive candidates; (c) patterns done manually 3+ times -> new skill/rule candidates.
- Propose. On a branch
vulyk/evolve-<date>, write the actual diffs: edits toCLAUDE.mdproject profile,.claude/rules/, agent prompts, new skill scaffolds; move archived skills to.claude/skills/_graveyard/<name>/addingRETIRED.md(date, reason, evidence). Append a CHANGELOG.md entry justifying EVERY change in one line each. - Human gate. Present the changeset as a review: per-change rationale, expected effect, rollback note. Apply NOTHING to the main branch yourself. With
--dry-run, stop after the diagnosis report.
Discipline notes: prefer deleting and tightening over adding - constitutions rot by accretion; a rule that fires rarely but prevents disasters stays (frequency is not the only signal - say when you keep something for severity reasons).
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.
- 5d ago First seen · 14 lines · 23 tokens per session scan A dbed3e71ca41
vulyk-evolve is a command published in the GitHub repository Black-coffe/vulyk (2 stars, last pushed yesterday), licensed MIT. It adds 23 tokens to every session and 392 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
psm
/oh-my-claudecode:psm is a compatibility alias for /oh-my-claudecode:project-session-manager.
project
Generate project documentation (product.md, structure.md, tech.md, codemaps/).
version
Display current guide and Claude Code versions.
discover
Run a full product discovery cycle — from outcome definition through opportunity mapping, prioritisation, and experiment design. Use when the team isn't sure what to build next, or before writing a PRD for a complex feature space.
resume
Resume a previous session. Reads recent session logs, open tasks, and last decisions — gives Claude full context without re-explaining the project.
diff-docs
Compare official Anthropic docs baseline vs current snapshot (no network — instant).