Borrowing it
Nothing to install: this file belongs to vepo/issues. 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/vepo/issues/main/CLAUDE.mdgit clone --depth 1 https://github.com/vepo/issuesWrote 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/vepo/issues/claude-md)<a href="https://agentmods.dev/instructions/vepo/issues/claude-md"><img src="https://agentmods.dev/badge/instructions/vepo/issues/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/vepo/issues/claude-md"><img src="https://agentmods.dev/badge/instructions/vepo/issues/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.01833 | $0.01833 |
| Opus 5.5 | $0.00733 | $0.00733 |
| Sonnet 5.5 | $0.00367 | $0.00367 |
| Haiku 4.5 | $0.00183 | $0.00183 |
Grade A, and why
issues 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 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.
How it starts
The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
@AGENTS.md
Mandatory development process — read before touching src/
This repo enforces a strict five-phase gate on every non-trivial change (new behaviour, API, UI route, schema, multi-package refactor, or cross-feature bug fix). Full detail: .cursor/rules/development-process.mdc.
1. Feature analysis → 2. Architecture design → 3. Task break → 4. Explicit task approval → 5. TDD implementation
- No edits to
src/main/**,src/test/**, orsrc/main/webui/**before phase 4. Phases 1–3 only touchfeature/<slug>.md,docs/**, andARCHITECTURE.md. - Track open decisions as FQn (feature questions, phase 1) and AQn (architecture questions, phase 2) in the feature doc. Answering a question is not approval — after every FQ/AQ answer, run an impact review (update Impact, Wireframe, Architecture, Feature checklist, tasks) and stop.
- Phase 4 requires explicit task-ID approval ("Approve T1–T3", "Go ahead with T1"). "Implement it" / "yes" / "do the analysis" do not count — present the task table and ask which IDs to approve instead.
- Phase 5 is TDD only, per approved task: Red (failing test, no
src/mainchange) → Green (minimal code) → Refactor. Optionally delegate to.cursor/agents/tdd-red.md/tdd-green.md/tdd-refactor.md. - Skip the gate only for: typo, comment-only, formatter-only, or docs-only edits.
- Never end a session with broken code. Before stopping (task
doneor stillin-progress), the tree must compile and touched tests must pass — fix forward or revert, don't leave red. - Not in production yet — no legacy/back-compat concerns. Schema changes amend
V1.0.0__Database_Creation.sqldirectly (see.cursor/rules/issues-flyway.mdc); never add newV1.0.xmigration files.
Commands
# Backend
mvn quarkus:dev # run app (backend :8080 + Angular dev server via Quinoa on :4200)
mvn test # all backend tests
mvn test -Dtest=TicketEndpointTest#methodName # single test
mvn test -Dtest=ArchitectureTest # ArchUnit rules
mvn formatter:format # Java formatting
mvn verify # full backend gate — required before marking a task done
# After backend endpoint changes, regenerate the Angular API client
mvn test && cd src/main/webui && npm run generate:api
# Frontend (src/main/webui)
npm run build # production build; runs generate:api via prebuild — use this, not bare `ng build`
npm test -- --no-watch --browsers=ChromeHeadless # headless test run
npm run lint
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 · 80 lines · 1,833 tokens per session scan A d3056fee92c2
issues CLAUDE.md is an instructions file published in the GitHub repository vepo/issues (8 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 1,833 tokens to every session, about $0.0073 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.