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/vepo/issues/agents-mdgit clone --depth 1 https://github.com/vepo/issuesWhat 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.02320 | $0.02320 |
| Opus 5 | $0.01160 | $0.01160 |
| Sonnet 5 | $0.00464 | $0.00464 |
| Haiku 4.5 | $0.00232 | $0.00232 |
Grade A, and why
issues AGENTS.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.
How it starts
The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent instructions (Issues)
Read these before changing code or tests:
| Document | Purpose |
|---|---|
| ARCHITECTURE.md | Stack, packages, patterns, API map, naming, feature workflow |
| docs/domain-specification.md | Ubiquitous language, bounded contexts, invariants |
| docs/feature-catalog.md | UI routes and navigation paths |
| docs/backlog.md | Ordered product backlog (ideas and priority) |
| docs/ui-elements-gallery.md | UI element catalog — flat UI principles, properties, style, behavior |
| docs/conventions-checklist.md | Doc debt and agent setup status |
| feature/ | Feature analysis, tasks, approval, and changelog per capability |
| .cursor/rules/ | Four pillars + file-scoped detail |
| .cursor/agents/ | Project subagents (specialized behaviour) |
| .cursor/skills/issues-agent/ | Backup skill: use Issues via MCP / API tokens |
Not in production yet: This project is not in production yet. There is no need to keep legacy or update any production environment. Schema changes: amend V1.0.0__Database_Creation.sql only — see issues-flyway.mdc.
Development process: development-process.mdc — (1) feature analysis → (2) architecture design → (3) task break → (4) explicit task approval → (5) TDD. Each feature doc has Wireframe and Architecture sections; each changelog entry maintains a Feature checklist (FCn) rechecked before done. Two question kinds: FQn (product) and AQn (technical). Answering FQ/AQ triggers a mandatory impact review (not approval). No code before approved task IDs. Never end with non-working code — mvn verify green before stopping.
API codegen: after backend endpoint changes, run mvn test then cd src/main/webui && npm run generate:api. Endpoints live in {context}.{action} subpackages — one HTTP method per class (e.g. user.create.CreateUserEndpoint).
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 · 112 lines · 2,320 tokens per session scan A f628186e39f3
issues AGENTS.md is an instructions file published in the GitHub repository vepo/issues (8 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 2,320 tokens to every session, about $0.0116 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-31.
Other instructions, from other repositories
spartan CLAUDE.md
Instructions for spartan-ng/spartan, covering working in this repo (notes for claude / ai agents), before pushing: run the ci checks locally and pull requests.
fundamental-ngx AGENTS.md
Instructions for SAP/fundamental-ngx, covering angular 22+ development guidelines, persona, quick reference, essential commands and build/lint/test specific library.
primitives CLAUDE.md
Instructions for radix-ng/primitives, covering radix ng primitives — claude guide, project knowledge, project overview, monorepo structure and naming conventions.
openbridge-webcomponents watch-radial-instruments.instructions.md
Instructions for Ocean-Industries-Concept-Lab/openbridge-webcomponents, covering watch & radial instruments, architecture overview, key principle: logic in watch.ts, instruments stay thin, shared sibling modules and layering & stacking pattern.
openbridge-webcomponents line-area-charts.instructions.md
Instructions for Ocean-Industries-Concept-Lab/openbridge-webcomponents, covering line/area charts & gauge trend, architecture overview, key principle: logic in base class, subclasses stay thin, base class architecture and line graph (non-filled).
openbridge-webcomponents setpoint.instructions.md
Instructions for Ocean-Industries-Concept-Lab/openbridge-webcomponents, covering setpoint system, architecture overview, when to use mixin vs bundle, setpointmixin usage and setpointbundle usage.