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-platform)<a href="https://agentmods.dev/rules/vepo/issues/issues-platform"><img src="https://agentmods.dev/badge/rules/vepo/issues/issues-platform/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-platform"><img src="https://agentmods.dev/badge/rules/vepo/issues/issues-platform.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.00517 | $0.00517 |
| Opus 5.5 | $0.00207 | $0.00207 |
| Sonnet 5.5 | $0.00103 | $0.00103 |
| Haiku 4.5 | $0.00052 | $0.00052 |
Grade A, and why
issues-platform 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
Platform usage
Stack boundaries
| Layer | Technology | Location |
|---|---|---|
| Backend | Java 21, Quarkus 3.30 | src/main/java/dev/vepo/issues/ |
| Frontend | Angular 20, TypeScript | src/main/webui/ |
| Database | PostgreSQL + Flyway | src/main/resources/db/migration/ |
| SPA integration | Quarkus Quinoa | application.properties quarkus.quinoa.* |
| Build | Maven (root), npm (webui) | pom.xml, src/main/webui/package.json |
Approved libraries
- Backend: Jakarta EE (REST, CDI, Persistence, Validation), SmallRye JWT/OpenAPI, Quarkus Mailer, Hibernate ORM, REST Assured (tests), ArchUnit (tests).
- Frontend: Angular Material, Chart.js/ng2-charts,
@jsverse/transloco8.4.x for reactive runtime PT/EN catalogs, standard Angular CLI toolchain. - Logging: SLF4J only in Java — never
System.out.
Local development
mvn quarkus:dev # Backend + Quinoa dev server (Angular on :4200)
mvn test # Backend tests
mvn formatter:format # Java formatting
CI alignment
.github/workflows/build.yml— Sonar: Angular tests +mvn verify..github/workflows/maven.yml—mvn package.
Never
- Add Python or unrelated runtimes for repo tooling.
- Change JWT key paths without updating
%devand test config. - Use
VOorDTOsuffix on HTTP types — useRequest/Response. - Bypass Flyway for schema changes — update SQL per issues-flyway.mdc.
- Commit secrets from
application.propertiesdev mailer block to production config. - Reintroduce locale-prefixed routes or locale-specific Angular builds — UI locale changes at runtime on canonical routes.
Package naming
Root package: dev.vepo.issues. Maven artifact: issues. Product name: Issues.
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 · 517 tokens per session scan A dc317959ed96
issues-platform is a cursor rule published in the GitHub repository vepo/issues (8 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 517 tokens to every session, about $0.0021 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.