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/issues-core)<a href="https://agentmods.dev/rules/vepo/issues/issues-core"><img src="https://agentmods.dev/badge/rules/vepo/issues/issues-core/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/issues-core"><img src="https://agentmods.dev/badge/rules/vepo/issues/issues-core.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.00476 | $0.00476 |
| Opus 5.5 | $0.00190 | $0.00190 |
| Sonnet 5.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 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.
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.
- 1mo ago 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 2mo ago), licensed Apache-2.0. It adds 476 tokens to every session, about $0.0019 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
project-context
EDDI Backend — AI Agent Instructions. Complete project context, architecture, and coding guidelines.
api-property-optionality-hygiene
Fix ApiProperty/ApiPropertyOptional optionality mismatches in DTO files; use for scheduled batch fixes or DTO edits.
shared-libraries
Shared libraries - condition framework, inventory containers, file-backed DB, itinerary, references.
pages
Source: docs/agents/pages.md Regenerate: npm run agents:sync -w packages/openbridge-webcomponents -->.
go
Cursor rule "go" from supertokens/create-supertokens-app, covering go and examples.
php-client-implementation
Guidelines for implementing MCP clients in PHP.