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-gc.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-gc)<a href="https://agentmods.dev/commands/black-coffe/vulyk/vulyk-gc"><img src="https://agentmods.dev/badge/commands/black-coffe/vulyk/vulyk-gc.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.00170 |
| Opus 5 | $0.00007 | $0.00085 |
| Sonnet 5 | $0.00003 | $0.00034 |
| Haiku 4.5 | $0.00001 | $0.00017 |
Grade A, and why
vulyk-gc 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 8d 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
Dispatch librarian for a full GC pass over memory/ per its protocol (consolidate learnings, flag stale maps, prune snapshots >14 days, verify the pointer index).
Then act on its report in the main session:
- Stale maps -> offer to run
/vulyk-mapfor the flagged modules now. - "Needs human decision" items -> present them as a short list, decide nothing unilaterally.
- If
memory/learnings/CONSOLIDATED.mdexceeded its 40-entry cap, note that the next/vulyk-evolveshould promote the oldest stable entries into rules or wiki notes (learnings are a buffer, not an archive).
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.
- 8d ago First seen · 12 lines · 14 tokens per session scan A e46ad57fb5cb
vulyk-gc 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 170 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
retex
Retex - Capture lesson learned dans memory après fix, rollback, erreur.
evolve
A knowledge-review workflow that groups repeated lessons and turns them into reusable commands, automatic skills, or separate agents. A command is user-triggered, a skill is an automatic behaviour, and an agent handles a complex multi-step task.
memory
A project-memory manager that keeps current progress, technical decisions, problems, and reusable patterns in Markdown files inside a memory-bank folder.
status
A project-status command that checks a code repository and its supporting project notes. The supplied description is in Chinese and lists checks for Git, a memory bank, dependencies, environment settings, components, and conflicts.
context
A project-context manager for coding-agent sessions. It loads the project’s goals, technology choices, constraints, current phase, related documents, and task details from files such as progress.md.
catchup
A command for quickly rebuilding project context after the conversation has been cleared. It reads key project documents, recent Git changes, and available session history, then summarizes the current state.