Borrowing it
Nothing to install: this file belongs to byh3071-cpu/vhk. 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/byh3071-cpu/vhk/main/.agents/skills/vhk-evolve-loop/SKILL.mdgit clone --depth 1 https://github.com/byh3071-cpu/vhkWrote 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/skills/byh3071-cpu/vhk/vhk-evolve-loop)<a href="https://agentmods.dev/skills/byh3071-cpu/vhk/vhk-evolve-loop"><img src="https://agentmods.dev/badge/skills/byh3071-cpu/vhk/vhk-evolve-loop.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00029 | $0.00298 |
| Opus 5 | $0.00015 | $0.00149 |
| Sonnet 5 | $0.00006 | $0.00060 |
| Haiku 4.5 | $0.00003 | $0.00030 |
Grade A, and why
vhk-evolve-loop 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
VHK Evolve Loop
프로젝트 개선의 정본 흐름은 .vhk/memory.json → vhk evolve → RULES.md다. VHK CLI 자체의
결함은 vhk-dogfood-issue로 보낸다.
기록과 패턴
vhk learn "한 줄 교훈 — 원인 포함"
vhk win "한 줄 성공 — 유지할 이유 포함"
vhk pattern detect
vhk pattern list
vhk evolve suggest
vhk evolve list
팀 공유가 필요하면 프로젝트 기록 규약에 맞는 recurring-defects 문서나 ADR을 사용한다.
반영
- 입력 가능한 세션과 사람 확인이 있으면
vhk evolve apply <id>뒤vhk sync를 실행한다. - 입력할 수 없는 에이전트는
vhk evolve digest로 초안만 제안하며 자동 적용하지 않는다. - 같은 교훈이 둘 이상의 VHK 프로젝트에서 확인되면 공개 템플릿 개선 후보로 검토한다.
CLI 결함을 learn만으로 끝내거나, 로컬 memory만 바꾸고 공유할 RULES.md를 갱신한 것처럼 말하지 않는다.
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 · 31 lines · 29 tokens per session scan A b43f5a3ff584
vhk-evolve-loop is a skill published in the GitHub repository byh3071-cpu/vhk (12 stars, last pushed today), licensed MIT. It adds 29 tokens to every session and 298 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-30.
Other skills, from other repositories
crit-cli
Use when an agent needs to author or reply to crit inline comments programmatically (including multi-agent workflows commenting on shared code/plans/docs/proposals), publish or unpublish a crit review with crit share, sync a crit review to or from a GitHub PR or GitLab MR, or read/interpret a crit review JSON file.…
crit
Review code changes, a plan, a live page (running dev server), or a local HTML file with Crit inline comments and structured human feedback. Use only when the user explicitly invokes /crit or directly asks to use Crit; a generic review request does not count.
crit-story
Author a crit story only when the user explicitly invokes crit-story or directly asks you to generate a crit story. Do not infer this skill from generic review, PR, or diff-review requests.
ospec
Document-driven OSpec workflow for initialization, change/goal routing, validation, archiving, and durable project knowledge.
ospec-change
Create or advance a lightweight OSpec change using the classic fast workflow.
git-release
Draft release notes from merged PRs, propose a semver bump, and emit a copy-pasteable gh release create command. Use when preparing a tagged GitHub release.