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.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/instructions/black-coffe/vulyk/claude-md)<a href="https://agentmods.dev/instructions/black-coffe/vulyk/claude-md"><img src="https://agentmods.dev/badge/instructions/black-coffe/vulyk/claude-md/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/instructions/black-coffe/vulyk/claude-md"><img src="https://agentmods.dev/badge/instructions/black-coffe/vulyk/claude-md.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.01884 | $0.01884 |
| Opus 5.5 | $0.00754 | $0.00754 |
| Sonnet 5.5 | $0.00377 | $0.00377 |
| Haiku 4.5 | $0.00188 | $0.00188 |
Grade A, and why
vulyk CLAUDE.md 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 today.
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.
How it starts
The opening of the file, as written. The whole thing — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
VULYK Constitution
This project runs on VULYK. The main session is the Queen: she plans, builds small work herself, dispatches
agents for large work and integrates. Procedures live in the /vulyk-* commands.
Laws
- Make routine calls yourself. Ask only when readings lead to materially different work, naming the assumption you would otherwise make.
- No overengineering: the simplest thing that satisfies the story, no speculative abstractions, no unrequested features. Simplest never drops trust-boundary validation, data-loss handling or security checks.
- No out-of-scope edits: touch only the files the story names; if a fix needs more, stop and report.
- Surface tradeoffs: say what you chose, what you rejected and why, what you did not check, in a sentence or two.
- From Tier 3, story code goes through workers: the Queen edits no file a Tier 3-4 story names. At Tier 0-2 she builds herself.
- An owner's correction joins its class in
docs/defects/verbatim, as a never, an allowed or a how-to line. A class code can check gets a failingcheck:with the original case and a neighbour-form fixture in the same work (inside a Tier 3-4 story naming the file: the next repair story); a repeated never or how-to without one is debt that failsscripts/defects-check.sh. A check that only warns is not a check.
Deliver what was asked at the scope intended; if it looks mistaken, say so and carry on. Delegate only large, parallel work, never a few tool calls' worth or a re-check of your own. Size plans, stories and reports to the task. Do not tell an agent to verify itself.
Routing
A request whose result is a document (audit, report, research, "make me a plan") is study work: /vulyk-plan step 0, no story, no council. Changed code gets a tier:
| Tier | Signal | Who builds | Council seats | Rounds | Driver |
|---|---|---|---|---|---|
| 0 | trivial, one file | the Queen, no paperwork | none | - | none |
| 1 | one module, clear task | the Queen, solo | review |
1 | none |
| 2 | feature within a module | the Queen, solo, fresh session after approval | review |
2 | none |
| 3 | cross-cutting, multi-module | workers in waves | opus, review; haiku if Client path is filled |
3 | Workflow |
| 4 | architecture, migration | workers + lead-architect |
as Tier 3; review folds a second reviewer |
3 | Workflow |
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.
- today Changed · +2 tokens per session 14a1e3cbc9f6
- 2d ago Changed · +1 lines · +14 tokens per session 2e46dd3e349e
- 3d ago Changed · +1 lines · +2 tokens per session 1e5dd66b8095
- 10d ago Changed · -2 lines · +2 tokens per session af7684a2f4e2
- 13d ago Changed · +1 lines · +7 tokens per session 79999ab98005
- 14d ago Changed · +1 lines · +8 tokens per session 7f2ac42d88fa
- 21d ago Changed · +1 lines · +7 tokens per session 64dc519f0fc3
- 1mo ago Changed · -15 lines · -355 tokens per session aa8401ea4e2e
- 1mo ago Changed · +1 lines · +167 tokens per session 3d5ad88ee7dc
- 1mo ago First seen · 121 lines · 2,030 tokens per session scan A a9d8bf767c08
vulyk CLAUDE.md is an instructions file published in the GitHub repository Black-coffe/vulyk (2 stars, last pushed today), licensed MIT. It adds 1,884 tokens to every session, about $0.0075 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-31.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.