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.
npx agentmods add rules/e-gov/cursor-prompts/integration-standardsgit clone --depth 1 https://github.com/e-gov/cursor-promptsWrote 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/e-gov/cursor-prompts/integration-standards)<a href="https://agentmods.dev/rules/e-gov/cursor-prompts/integration-standards"><img src="https://agentmods.dev/badge/rules/e-gov/cursor-prompts/integration-standards.svg" alt="Measured on agentmods" 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 | $0.00737 | $0.00737 |
| Opus 5 | $0.00368 | $0.00368 |
| Sonnet 5 | $0.00147 | $0.00147 |
| Haiku 4.5 | $0.00074 | $0.00074 |
Grade A, and why
integration-standards 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 3d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Integration Standards
Context
- Apply when developing REST APIs, message queues, or cross-system integrations
- Ensures consistent patterns across different integration types
- Focuses on automatically verifiable pattern validation
Requirements
API Design Patterns
- Use resource-based URLs:
/Xfor collections,/X/{id}for specific resources - Use kebab-case for multi-word resources:
/boat-engines - Use standard HTTP methods: GET (read), POST (create), PUT (replace), PATCH (partial update), DELETE (remove); use HEAD/OPTIONS where applicable
- Include API version in URL path:
/v1/persons - Return appropriate HTTP status codes: 200, 201, 202, 204, 400, 401, 403, 404, 409, 422, 429, 500, 503
- Use RFC 7807 Problem Details for errors (type, title, status, detail, instance); include application error code and traceId/correlationId
- Use query parameters for filtering:
GET /persons?name=John&age=25 - Implement pagination for large result sets:
?limit=25&offset=50 - Document APIs using OpenAPI specification (mandatory)
- Follow Contract-First approach (define OpenAPI spec before implementation)
- Include JSON schema definitions for all data structures
Message Queue Patterns
- Use channel naming convention:
[data_owner].[message_data] - Add type suffixes: Request/Response, Topic, Queue
- Use JSON format for all messages unless binary data required
- Validate JSON messages using json-schema validator
- Include correlation-id for request-response patterns
- Encode binary files as Base64 in JSON messages
Security & Error Handling
- Use HTTPS protocol for all cross-system communication
- Use OAuth 2.1/OpenID Connect with Bearer tokens in the
Authorizationheader; NEVER include tokens in URLs or query parameters - Validate SSL certificates for secure connections
- Include correlation IDs in all integration requests and propagate W3C Trace Context headers (
traceparent,tracestate) - Return RFC 7807 Problem Details for error responses
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.
- 3d ago First seen · 90 lines · 737 tokens per session scan A 87000318ea9a
integration-standards is a cursor rule published in the GitHub repository e-gov/cursor-prompts (34 stars, last pushed 4mo ago), licensed MIT. It adds 737 tokens to every session, about $0.0037 per session on Opus 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-30.
Other cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.