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.
git 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/rules/byh3071-cpu/vhk/ecosystem)<a href="https://agentmods.dev/rules/byh3071-cpu/vhk/ecosystem"><img src="https://agentmods.dev/badge/rules/byh3071-cpu/vhk/ecosystem/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.
<a href="https://agentmods.dev/rules/byh3071-cpu/vhk/ecosystem"><img src="https://agentmods.dev/badge/rules/byh3071-cpu/vhk/ecosystem.svg" alt="Reviewed on agentmods" width="80" 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.00318 | $0.00318 |
| Opus 5.5 | $0.00127 | $0.00127 |
| Sonnet 5.5 | $0.00064 | $0.00064 |
| Haiku 4.5 | $0.00032 | $0.00032 |
Grade A, and why
ecosystem 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 1mo 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 Project Boundaries (Cursor-only)
- 실행 계층(vhk 명령)은 에이전트 무관 — 어떤 AI 에이전트가 실행해도 vhk 명령 자체는 동일하게 동작.
- 트리거 계층은 도구별 기능을 따른다 — 자동 훅이 없는 에이전트에서는
vhk context와vhk verify를 명시적으로 실행한다. - Cursor — Composer batch/repeat 보조; 코딩·반복 작업용.
- Project rules — 이 저장소의
AGENTS.md와RULES.md를 우선한다. 별도 사용자 규칙 파일은VHK_RULES_FILE또는vhk config set-rules-file로 연결한다. - Concurrency — same repo + same branch에 에이전트 2개 금지; parallel은 worktree (
vhk worktree/ Cursor--worktree). - Derived files —
AGENTS.md·.cursorrules손수 편집 금지 →RULES.md수정 후vhk sync..cursor/agents/에.claude/agents/중복 금지.
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.
- 1mo ago First seen · 18 lines · 318 tokens per session scan A 496f36cd6e03
ecosystem is a cursor rule published in the GitHub repository byh3071-cpu/vhk (12 stars, last pushed yesterday), licensed MIT. It adds 318 tokens to every session, about $0.0013 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-30.
Other cursor rules, from other repositories
frontend-architecture
Cursor rule "frontend-architecture" from tomasz-tomczyk/crit, covering frontend architecture, two-paradigm page fork, module pattern, shared modules (used by both modes) and code-review modules (used only by code-review mode).
proxy-auth-transport
Every CLI command or browser UI action that calls a crit-web API must work in both modes.
frontend-js
Cursor rule "frontend-js" from tomasz-tomczyk/crit, covering frontend js rules (semantic — eslint handles syntax/style), dom & events, state management, persisted settings (cookies, not localstorage) and error handling.
go
Cursor rule "go" from tomasz-tomczyk/crit, covering go code rules (semantic — linters handle syntax/style), struct & state integrity, code organization, git operations and daemon/server.
frontend-css
Cursor rule "frontend-css" from tomasz-tomczyk/crit, covering css rules, responsive & touch and selectors.
forge-core
Core Forge project conventions — always applied.