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-model)<a href="https://agentmods.dev/rules/vepo/issues/issues-model"><img src="https://agentmods.dev/badge/rules/vepo/issues/issues-model/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-model"><img src="https://agentmods.dev/badge/rules/vepo/issues/issues-model.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.01009 | $0.01009 |
| Opus 5.5 | $0.00404 | $0.00404 |
| Sonnet 5.5 | $0.00202 | $0.00202 |
| Haiku 4.5 | $0.00101 | $0.00101 |
Grade A, and why
issues-model 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Building the model
Canonical references: ARCHITECTURE.md, docs/domain-specification.md.
Before any change
- Development process — follow development-process.mdc: feature analysis → architecture design → task break → user approval → TDD. No
src/mainorsrc/testchanges before approval. - Feature analysis — create or update
feature/<feature-slug>.mdper change-request-analysis.mdc; maintain Wireframe, Feature checklist, and Architecture (architecture-design.mdc). - Read domain specification (Ubiquitous Language) for ticket, workflow, project, or notification work.
- Read ARCHITECTURE.md §5 (package layout), §11 (naming), §12 (feature workflow).
- Follow patterns in the package you edit.
Domain vocabulary in code and tests
- Use domain terms:
Ticket,Workflow,Transition,Subscriber,Identifier— notData,ItemDTO,stateFlag. - Test names:
shouldMoveTicketWhenTransitionIsValid()— full narrative in issues-tests.mdc.
Package placement
| Change | Package |
|---|---|
| Auth, JWT, login | auth |
| Users, roles | user |
| Projects | project |
| Workflows, statuses, transitions | workflow |
| Tickets, comments, history | ticket, ticket.* |
| Categories | categories |
| SSE notifications | notifications |
| Dashboard widgets | dashboards |
mailer |
|
| Cross-cutting HTTP/errors | infra |
Bounded context rules: issues-bounded-contexts.mdc.
After model-affecting changes
| Trigger | Update |
|---|---|
| New domain terms or invariants | domain-specification.md |
| New/changed UI route or flow | feature-catalog.md |
| New/changed user-facing capability | README.md § Features — readme.mdc |
| Structure, API surface, known gaps | ARCHITECTURE.md §13 |
| User-facing docs | documentation.mdc |
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 · 73 lines · 1,009 tokens per session scan A 7f61054c5ee5
issues-model is a cursor rule published in the GitHub repository vepo/issues (8 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 1,009 tokens to every session, about $0.0040 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.