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 rules/vepo/issues/documentationgit 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.00000 | $0.00479 |
| Opus 5 | $0.00000 | $0.00239 |
| Sonnet 5 | $0.00000 | $0.00096 |
| Haiku 4.5 | $0.00000 | $0.00048 |
Grade A, and why
documentation 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 yesterday.
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
Documentation — read and maintain
Before changing API or user-visible behaviour
- Skim AGENTS.md doc map.
- Update the lowest complexity doc that covers the feature.
After changes — update when relevant
| Change | Update |
|---|---|
| New domain term or invariant | domain-specification.md |
| New/changed UI route | feature-catalog.md |
| New/changed UI element (class, component, pattern) | ui-elements-gallery.md |
| Flat UI / visual language change | ui-elements-gallery.md § Flat UI + issues-ux.mdc |
| Package, API surface, patterns | ARCHITECTURE.md |
| Doc debt closed | conventions-checklist.md |
| New/changed user-facing feature | README.md § Features — see readme.mdc |
| New product idea (not yet analyzed) | backlog.md — ordered table; see backlog-management.mdc |
| README badges or project name | README.md |
Complexity order
- domain-specification — vocabulary and rules
- feature-catalog — routes and click paths
- ui-elements-gallery — reusable UI components and patterns
- ARCHITECTURE — technical structure
- README — pitch and links
Quality bar
- No stale type names after renames — grep docs when renaming.
- Cross-link; avoid duplicating large blocks.
Related
- Agent index: AGENTS.md
- Docs sync subagent: docs-sync.md
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.
- yesterday First seen · 48 lines · 0 tokens per session scan A 97e2acfc39e9
documentation is a cursor rule published in the GitHub repository vepo/issues (8 stars, last pushed 1mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 479 tokens. 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 cursor rules, from other repositories
project-context
EDDI Backend — AI Agent Instructions. Complete project context, architecture, and coding guidelines.
testing-visual
Source: docs/agents/testing-visual.md Regenerate: npm run agents:sync -w packages/openbridge-webcomponents -->.
com-example-service-PublicPaymentController
AI rules for com.example.service.PublicPaymentController.
front-vue-page-conventions
YiSmartCloud front-end Vue page conventions.
cursorrules
Cursor rule "cursorrules" from Forge-Space/ui-mcp, covering uiforge mcp cursor rules, environment setup, development guidelines, component library integration and figma integration.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.