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-testing)<a href="https://agentmods.dev/rules/vepo/issues/issues-testing"><img src="https://agentmods.dev/badge/rules/vepo/issues/issues-testing/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-testing"><img src="https://agentmods.dev/badge/rules/vepo/issues/issues-testing.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.00647 | $0.00647 |
| Opus 5.5 | $0.00259 | $0.00259 |
| Sonnet 5.5 | $0.00129 | $0.00129 |
| Haiku 4.5 | $0.00065 | $0.00065 |
Grade A, and why
issues-testing 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing
Run the smallest scope that catches your regression after substantive edits. Full gate: mvn verify once before marking done — see issues-quality.mdc.
Session end: never stop with failing tests in your diff — run at least the affected test class, then mvn verify before handing off (development-process.mdc § Working code invariant).
Tiered ladder
| When | Command |
|---|---|
| Trivial / compile-only edit | Skip until next substantive change |
| One backend package edited | Single test class or mvn test -Dtest=ClassName |
| REST endpoint changed | Related *EndpointTest + ArchitectureTest if DTOs changed |
| Angular component/service changed | cd src/main/webui && npm run build then npm test -- --include='**/affected.spec.ts' |
| Task done (backend) | mvn verify |
| Task done (full-stack) | mvn verify + npm run build + Angular tests (CI runs both) |
# All backend tests
mvn test
# Single test
mvn test -Dtest=TicketEndpointTest#methodName
# Architecture rules
mvn test -Dtest=ArchitectureTest
# Frontend (headless)
cd src/main/webui && npm run build
cd src/main/webui && npm test -- --no-watch --browsers=ChromeHeadless
# Dev mode (manual)
mvn quarkus:dev
Impact map
| You changed | Run |
|---|---|
ticket/* |
TicketEndpointTest, TicketHistoryServiceTest |
auth/*, user/* |
AuthenticationEndpointTest, UserEndpointTest |
project/* |
ProjectEndpointTest |
workflow/* |
WorkflowEndpointTest |
*Request/*Response records |
ArchitectureTest + affected endpoint tests |
| Angular service | Matching *.service.spec.ts |
| Angular component | Matching *.component.spec.ts |
Detail: issues-tests.mdc.
TDD development guidance: issues-model.mdc § TDD.
When tests fail
- Re-run smallest repro — issues-test-failure-diagnosis.mdc.
- Do not loop full
mvn verifyper fix. - After green: one report under
reports/per that rule.
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 · 68 lines · 647 tokens per session scan A 41347790fd5a
issues-testing is a cursor rule published in the GitHub repository vepo/issues (8 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 647 tokens to every session, about $0.0026 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
always-on
Spec-driven Spring Boot 4 — global guardrails that compensate for Windsurf's lack of a pre-tool-use hook.
testing-visual
Source: docs/agents/testing-visual.md Regenerate: npm run agents:sync -w packages/openbridge-webcomponents -->.
production-code
Production code rule — TDD precondition + Spring Boot 4 conventions.
test-code
Test code rule — JUnit 5, Testcontainers, traceability tagging.
fuzzing
Fuzzing setup and guidelines for skia-rs.
testing
Testing conventions for Ion Design System using Jest and Angular Testing Library.