ecosystem

A set of project-boundary rules for using VHK with Cursor and other AI agents. It explains which commands work across agents, which files are generated, and how agents should work in parallel.

In plain words
What is it for?
Use it to decide which rules and commands take priority, connect custom rule files, synchronize generated files, and isolate parallel work in separate worktrees.
Why use it?
It prevents agents from editing generated files directly or running conflicting sessions in the same branch. It also provides alternatives when an agent has no automatic hooks.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/byh3071-cpu/vhk/ecosystem
Clone the repo
git clone --depth 1 https://github.com/byh3071-cpu/vhk

Made for: Cursor.

Per session 318 This file is loaded in full into every session.
When invoked 318 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.00318 $0.00318
Opus 5 $0.00159 $0.00159
Sonnet 5 $0.00064 $0.00064
Haiku 4.5 $0.00032 $0.00032

Measured 3d ago against content hash 496f36cd6e03, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 3d 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.

.cursor/rules/ecosystem.mdc · 18 lines

What it actually says

VHK Project Boundaries (Cursor-only)

  1. 실행 계층(vhk 명령)은 에이전트 무관 — 어떤 AI 에이전트가 실행해도 vhk 명령 자체는 동일하게 동작.
  2. 트리거 계층은 도구별 기능을 따른다 — 자동 훅이 없는 에이전트에서는 vhk contextvhk verify를 명시적으로 실행한다.
  3. Cursor — Composer batch/repeat 보조; 코딩·반복 작업용.
  4. Project rules — 이 저장소의 AGENTS.mdRULES.md를 우선한다. 별도 사용자 규칙 파일은 VHK_RULES_FILE 또는 vhk config set-rules-file로 연결한다.
  5. Concurrency — same repo + same branch에 에이전트 2개 금지; parallel은 worktree (vhk worktree / Cursor --worktree).
  6. Derived filesAGENTS.md·.cursorrules 손수 편집 금지 → RULES.md 수정 후 vhk sync. .cursor/agents/.claude/agents/ 중복 금지.
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. 3d ago First seen · 18 lines · 318 tokens per session scan A 496f36cd6e03

Subscribe to this mod's changes

ecosystem is a cursor rule published in the GitHub repository byh3071-cpu/vhk (12 stars, last pushed 3d ago), licensed MIT. It adds 318 tokens to every session, about $0.0016 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.