What is veche AGENTS.md?

Repository instructions for veche, including its project structure, naming rules, and specification-led development process. Spec-Driven Development means treating the written specification as the contract that code must follow.

Use it when editing veche to know which specification to read or update, how the code is organized, and which type checks, tests, and lint checks to run.

It prevents changes that conflict with the project's requirements and gives coding agents a fixed workflow for making and checking edits.

How cyberash-dev/veche configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to cyberash-dev/veche. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/cyberash-dev/veche/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/cyberash-dev/veche

Made for: Codex, OpenCode.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/cyberash-dev/veche/agents-md/github.svg)](https://agentmods.dev/instructions/cyberash-dev/veche/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/cyberash-dev/veche/agents-md"><img src="https://agentmods.dev/badge/instructions/cyberash-dev/veche/agents-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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/cyberash-dev/veche/agents-md"><img src="https://agentmods.dev/badge/instructions/cyberash-dev/veche/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 4,387 This file is loaded in full into every session.

When invoked 4,387 The same file — it is already loaded in full.

Security scan B 2 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.04387	$0.04387
Opus 5.5	$0.01755	$0.01755
Sonnet 5.5	$0.00877	$0.00877
Haiku 4.5	$0.00439	$0.00439

Measured 2mo ago against content hash 447a89f63d2c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade B, and why

veche AGENTS.md scanned grade B with 2 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 2mo 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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

(`~/.claude.json`, `~/.codex/config.toml`, `~/.hermes/config.yaml`) are NEVER edited

Runs shell commandslowCapability

Expected in a hook, worth knowing in a rule or an instructions file.

`node:child_process` for `--open`). If a dep feels needed, ask first.

AGENTS.md · 307 lines

How it starts

The opening of the file, as written. The whole thing — 307 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AGENTS.md

Conventions for any AI agent (Codex, Claude Code, Cursor, Aider, …) editing this repository. This file is the single source of truth; CLAUDE.md points here.

The non-negotiable rule

Spec-Driven Development. The specification in spec/spec.md is the contract. Code that diverges from the spec is a bug.

The workflow for any non-trivial change is:

Read the relevant spec file(s).
Update the spec first. Get human approval if the change is substantive.
Only then modify code to match.
Run npm run typecheck && npm test && npm run lint before declaring done.

Trivial changes (typo, obvious one-line fix, dependency bump) can skip step 2. When in doubt, change the spec first.

Project layout

veche/
├── spec/
│   └── spec.md            ← single monolithic contract; sections 1–19 +
│                            `## Partition: <name>` per feature
│                            (persistence, agent-integration,
│                            committee-protocol, meeting, web-viewer, install)
├── src/                   ← implementation, hexagonal + vertical slices
│   ├── features/<slice>/  ← one folder per Partition
│   ├── adapters/inbound/mcp/     ← MCP server (stdio)
│   ├── adapters/inbound/cli/     ← human-operator CLI (list, show, watch, install)
│   │                               + renderers + lib helpers
│   ├── adapters/inbound/web/     ← `veche watch` HTTP/SSE server
│   ├── infra/             ← composition root (DI wiring)
│   ├── bin/veche-server.ts  ← stdio MCP entrypoint
│   └── bin/veche.ts         ← CLI entrypoint
├── skills/veche/          ← canonical SKILL.md + optional UI metadata
├── examples/              ← sample .mcp.json, config.json
├── scripts/               ← repo helpers (e.g. sdd-approve-all.sh)
├── .sdd/                  ← SDD config + finalised approval plans
├── dist/                  ← build output (not committed locally)
└── node_modules/

Navigation: open spec/partitions/<name>.md for the slice you're touching. Each partition file is self-contained (Context, Glossary, Surfaces, Behaviours, Contracts, Invariants, Policies, Constraints, Migrations, Deltas, Open questions, Assumptions, Out-of-scope). The thin spec/spec.md is just an index.

Read the full file on GitHub · 307 lines

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.

2mo ago First seen · 307 lines · 4,387 tokens per session scan B 447a89f63d2c

Subscribe to this mod's changes

veche AGENTS.md is an instructions file published in the GitHub repository cyberash-dev/veche (21 stars, last pushed 5mo ago), licensed MIT. It adds 4,387 tokens to every session, about $0.0175 per session on Opus 5.5. A static security scan graded it B with 2 findings (reads agent configuration directories, runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

veche AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
veche AGENTS.mdcyberash-dev/veche	Instructions file	21	5mo ago	MIT	B	4,387	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	9,719	GitHub Copilot
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	5,516	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	today	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	today	MIT	A	4,680	Codex, OpenCode
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	3,093	GitHub Copilot
vscode model-prompts.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	2,022	GitHub Copilot

veche: Instructions file for Codex