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.
npx agentmods add instructions/cyberash-dev/veche/claude-mdgit clone --depth 1 https://github.com/cyberash-dev/vecheWhat 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 | $0.00464 | $0.00464 |
| Opus 5 | $0.00232 | $0.00232 |
| Sonnet 5 | $0.00093 | $0.00093 |
| Haiku 4.5 | $0.00046 | $0.00046 |
Grade A, and why
veche 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 2d 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
CLAUDE.md
Project-level guidance for Claude Code sessions on this repository.
Read
AGENTS.mdfirst. It is the single source of truth for conventions (architecture, naming, SDD workflow, testing, CLI/Watch/install invariants, adapter gotchas, build-break rules). This file only adds what is genuinely Claude-Code-specific and does not repeat anything from there.
Tools to prefer in this repo
The spec is large (~10k lines, sharded across spec/partitions/*.md) and the source tree is
hexagonal with deep slices. Lean on semantic navigation rather than Read:
mcp__code-skeleton__get_outline— file outline before reading.LSP.goToDefinition/LSP.findReferences/LSP.hover— for "where is X" / "who calls Y" / "type of Z" questions.Read— only when you need exact bytes for anEdit.Grep— for string/log/literal searches; not for symbol lookups.
Handoff etiquette
- Diffs stay small and focused: one spec change ↔ one code change ↔ one test change.
- End-of-turn summary is one or two sentences (outcome + risk/follow-up). No essays.
- Don't open
README.md,AGENTS.md, orCLAUDE.mdunless the task explicitly asks for it.
Claude-Code-specific notes about this committee
This project's committee can be entered by a Claude Code orchestrator AND can
have Claude Code as a member. The recursion guard documented in AGENTS.md →
Recursion guard is what makes that safe. If you ever see a nested
start_meeting from a child process, something is wrong with the guard —
debug, don't paper over.
--bare on claude -p is opt-in via extraFlags, never default — it breaks
OAuth login for most users. The recursion guard relies on
--strict-mcp-config --mcp-config '{"mcpServers":{}}', not on --bare.
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.
- 2d ago First seen · 41 lines · 464 tokens per session scan A 9ce66eaca17f
veche CLAUDE.md is an instructions file published in the GitHub repository cyberash-dev/veche (21 stars, last pushed 3mo ago), licensed MIT. It adds 464 tokens to every session, about $0.0023 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 instructions, from other repositories
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
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).
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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 oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.