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.
git 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/rules/vepo/issues/readme)<a href="https://agentmods.dev/rules/vepo/issues/readme"><img src="https://agentmods.dev/badge/rules/vepo/issues/readme/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/rules/vepo/issues/readme"><img src="https://agentmods.dev/badge/rules/vepo/issues/readme.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.00541 | $0.00541 |
| Opus 5.5 | $0.00216 | $0.00216 |
| Sonnet 5.5 | $0.00108 | $0.00108 |
| Haiku 4.5 | $0.00054 | $0.00054 |
Grade A, and why
readme 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
README maintenance
README.md is the public face of Issues — the first doc visitors and agents read. Keep it accurate whenever user-visible capabilities or onboarding change.
When to update README.md
| Trigger | Action in README |
|---|---|
| New user-facing feature shipped | Add bullet under the correct Features subsection |
| Feature removed or renamed | Update or remove the matching bullet |
| Tech stack change (framework, DB, auth) | Update Tech stack table |
| Dev startup or URLs change | Update Quick start commands and links |
New dev persona in dev-import.sql |
Update dev login table |
| Project name or Sonar badges change | Update title and badge URLs |
| New top-level doc agents should know | Add row to Documentation table |
What belongs in README vs other docs
| README | Elsewhere |
|---|---|
| One-line pitch, tech stack, quick start | — |
| Feature bullets (what the product does) | feature-catalog.md for routes, roles, click paths |
| Doc index links | Full detail in linked docs |
| Dev login table (summary) | Full personas in feature-catalog |
Do not duplicate route tables or API signatures in README — link to feature-catalog.md and ARCHITECTURE.md.
Feature bullet format
- Group under existing subsections (
Tickets & workflow,Projects & administration,Views & analytics,Notifications & email,Authentication) or add a new subsection if needed. - Start with bold term — short description.
- Use domain language from domain-specification.md.
Finish checklist
Before marking a feature task done when behaviour is user-visible:
- Update feature-catalog.md (routes and steps).
- Update README Features section (capability bullet).
- Update domain-specification.md if vocabulary changed.
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 · 53 lines · 541 tokens per session scan A 5439690476d7
readme is a cursor rule published in the GitHub repository vepo/issues (8 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 541 tokens to every session, about $0.0022 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 cursor rules, from other repositories
external-scale
Source: docs/agents/external-scale.md Regenerate: npm run agents:sync -w packages/openbridge-webcomponents -->.
ar
Source: docs/agents/ar.md Regenerate: npm run agents:sync -w packages/openbridge-webcomponents -->.
testing-visual
Source: docs/agents/testing-visual.md Regenerate: npm run agents:sync -w packages/openbridge-webcomponents -->.
integration-systems
Source: docs/agents/integration-systems.md Regenerate: npm run agents:sync -w packages/openbridge-webcomponents -->.
development-cycle
Source: docs/agents/development-cycle.md Regenerate: npm run agents:sync -w packages/openbridge-webcomponents -->.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.