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/issues-coregit 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.00476 | $0.00476 |
| Opus 5 | $0.00238 | $0.00238 |
| Sonnet 5 | $0.00095 | $0.00095 |
| Haiku 4.5 | $0.00048 | $0.00048 |
Grade A, and why
issues-core 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
Issues — core rules
Follow ARCHITECTURE.md and existing code in the same package.
Stack
- Quarkus REST + Hibernate ORM + PostgreSQL + Flyway.
- Angular SPA via Quinoa (
src/main/webui/). - JWT auth (SmallRye JWT); API base path
/api.
Endpoints
@ApplicationScoped+@Path; suffix*Endpoint.- Constructor injection for repositories and services.
- HTTP body types: Java
record, suffixRequest/Response— issues-http-contract.mdc. - Response mapping: static
load()factory on*Responserecords. - Security:
@DenyAllon class +@RolesAllowedon methods for protected resources.
Data access
- Repositories:
EntityManagerdirectly;Optionalfor single results;@Transactionalon mutating methods — issues-jpa.mdc. - Non-trivial domain logic:
@ApplicationScoped*Service(e.g.TicketHistoryService,MailerService). - Cross-cutting notifications: CDI events + SSE in
notifications.
Frontend
- Services in
src/main/webui/src/app/services/— HTTP calls to/api. - Components by feature folder under
components/. - Auth:
auth.guard.ts,auth.interceptor.tsfor Bearer token.
Never
System.out.println— use SLF4J.- Raw
VO/DTOsuffix on HTTP types. - Hardcode new API paths in multiple Angular files — centralize in services.
When adding a feature
development-process.mdc — feature analysis → architecture design → task break → explicit task approval → TDD. Answering FQ/AQ is not approval. Then ARCHITECTURE.md §12 — domain spec → package → tests → endpoint → Angular service/component → feature catalog.
When fixing a test
Understand failure first; fix production code or test data via Given. Do not weaken assertions.
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 · 49 lines · 476 tokens per session scan A 8a128bf9372d
issues-core is a cursor rule published in the GitHub repository vepo/issues (8 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 476 tokens to every session, about $0.0024 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 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.