What is api-standards?

A set of API development rules for Compozy, covering REST endpoints, JSON responses, errors, middleware, access control, rate limits, validation, and Swagger documentation.

Use it when creating or changing Compozy HTTP endpoints with Gin, especially when updating authentication, validation, errors, or Swagger annotations.

It gives API changes consistent conventions for routes, status codes, response shapes, and documentation. Swagger is a format and toolset for describing and viewing an API.

api-standards — Cursor rule for Cursor by compozy/gograph

Install

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.

Clone the repo

git clone --depth 1 https://github.com/compozy/gograph

Made for: Cursor.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/rules/compozy/gograph/api-standards/github.svg)](https://agentmods.dev/rules/compozy/gograph/api-standards)

Your own site

<a href="https://agentmods.dev/rules/compozy/gograph/api-standards"><img src="https://agentmods.dev/badge/rules/compozy/gograph/api-standards/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.

Your own site · 80×15

<a href="https://agentmods.dev/rules/compozy/gograph/api-standards"><img src="https://agentmods.dev/badge/rules/compozy/gograph/api-standards.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 305 This file is loaded in full into every session.

When invoked 305 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00305	$0.00305
Opus 5.5	$0.00122	$0.00122
Sonnet 5.5	$0.00061	$0.00061
Haiku 4.5	$0.00030	$0.00030

Measured 1mo ago against content hash 6217b5970a1c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

api-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 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.

.cursor/rules/api-standards.mdc · 54 lines

What it actually says

API Development Standards

Core Standards

<core_standards type="api_design">

RESTful design with consistent responses
Proper error responses with structured format
Use middleware for cross-cutting concerns
Implement proper authentication/authorization
Rate limiting and request validation </core_standards>

Implementation Guidelines

<implementation_guidelines type="api_conventions">

API versioned at /api/v0/
Use gin-gonic/gin for HTTP APIs
Consistent response formats across all endpoints
Proper HTTP status codes (200, 201, 400, 401, 403, 404, 500)
JSON response format with consistent error structure </implementation_guidelines>

Documentation Standards

<documentation_standards type="swagger">

MUST update Swagger annotations for all API changes
Generate docs at /swagger/index.html using swaggo/swag
Include request/response examples in annotations
Document all parameters, headers, and error responses </documentation_standards>

Response Format

<response_format type="standard">

// Success response
{
    "data": {...},
    "message": "Success"
}

// Error response
{
    "error": "Error message",
    "details": "Additional context"
}

</response_format>

Changes

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 · 54 lines · 305 tokens per session scan A 6217b5970a1c

Subscribe to this mod's changes

api-standards is a cursor rule published in the GitHub repository compozy/gograph (9 stars, last pushed 1y ago), licensed MIT. It adds 305 tokens to every session, about $0.0012 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.

Backend and APIs

api-standards

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

API Development Standards

Core Standards

Implementation Guidelines

Documentation Standards

Response Format

What this file has done since we first saw it

Other cursor rules, from other repositories

api-property-optionality-hygiene

python

cursor

django

shared-libraries

selectools-providers