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-http-contract)<a href="https://agentmods.dev/rules/vepo/issues/issues-http-contract"><img src="https://agentmods.dev/badge/rules/vepo/issues/issues-http-contract/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-http-contract"><img src="https://agentmods.dev/badge/rules/vepo/issues/issues-http-contract.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.00000 | $0.00331 |
| Opus 5.5 | $0.00000 | $0.00132 |
| Sonnet 5.5 | $0.00000 | $0.00066 |
| Haiku 4.5 | $0.00000 | $0.00033 |
Grade A, and why
issues-http-contract 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
HTTP contract
Enforced by ArchitectureTest (ArchUnit).
Naming
- Request — HTTP body or complex input:
CreateTicketRequest,MoveTicketRequest. - Response — HTTP output:
TicketResponse,TicketExpandedResponse. - Never use
VO,DTO, orVoprefix/suffix.
Shape
- All
*Requestand*Responsetypes MUST be Javarecord. - Endpoint public methods return
*Response,List<*Response>,Set<*Response>,Response, or SSEEvent. - Endpoint body parameters (non-path/query) MUST be
*Requestrecords.
OpenAPI
- Every endpoint class:
@Tag(name = "...")at class level,@Operation(operationId = "...")on the HTTP method. - Shared
*Request/*Responserecords live at context root (not inside endpoint classes). - Test profile exports spec to
target/openapi/openapi.yamlfor Angular codegen.
Examples
public record CreateTicketRequest(long projectId, String title, String description, Long categoryId) {}
public record TicketResponse(long id, String identifier, String title) {
public static TicketResponse load(Ticket ticket) { ... }
}
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 · 41 lines · 0 tokens per session scan A e500729996ca
issues-http-contract is a cursor rule published in the GitHub repository vepo/issues (8 stars, last pushed 2mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 331 tokens. 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.