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-bounded-contexts)<a href="https://agentmods.dev/rules/vepo/issues/issues-bounded-contexts"><img src="https://agentmods.dev/badge/rules/vepo/issues/issues-bounded-contexts/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-bounded-contexts"><img src="https://agentmods.dev/badge/rules/vepo/issues/issues-bounded-contexts.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.00398 | $0.00398 |
| Opus 5.5 | $0.00159 | $0.00159 |
| Sonnet 5.5 | $0.00080 | $0.00080 |
| Haiku 4.5 | $0.00040 | $0.00040 |
Grade A, and why
issues-bounded-contexts 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
Bounded contexts (modular monolith)
Single Maven module; logical boundaries in dev.vepo.issues.*. Full table: docs/domain-specification.md §Bounded contexts.
Context map
| Context | Packages |
|---|---|
| Platform | infra |
| Identity & access | auth, user |
| Project administration | project |
| Workflow configuration | workflow |
| Custom fields | customfield |
| Phase & version planning | phase |
| Ticket management | ticket, ticket.comments, ticket.history, ticket.business, ticket.attachments |
| Git / SCM | git |
| Classification | categories |
| Notifications | notifications |
| Analytics | dashboards |
mailer |
Dependency rules
- Feature packages may depend on packages listed in the domain spec for that row.
inframust not contain domain logic — only cross-cutting HTTP, errors, dev setup...*Repositorymust not depend on..*Endpoint(issues-layered-architecture.mdc).- Cross-context reactions (notify on ticket move): CDI events or services in the owning context — not direct repository access across unrelated packages.
Enforcement
ArchitectureTest enforces Request/Response naming and record usage. Extend with bounded-context ArchUnit rules when package boundaries stabilize.
When adding a feature
- Complete development-process.mdc — feature analysis, task break, user approval.
- Place code in the correct context package.
- Update domain spec if new vocabulary.
- Do not add domain imports to
infrabeyond what cross-cutting requires.
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 · 44 lines · 398 tokens per session scan A 44476ee6af83
issues-bounded-contexts is a cursor rule published in the GitHub repository vepo/issues (8 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 398 tokens to every session, about $0.0016 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.