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/abderrahimghazali/cursor-rules/api-standardsgit clone --depth 1 https://github.com/abderrahimghazali/cursor-rulesWhat 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.00000 | $0.00639 |
| Opus 5 | $0.00000 | $0.00319 |
| Sonnet 5 | $0.00000 | $0.00128 |
| Haiku 4.5 | $0.00000 | $0.00064 |
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 yesterday.
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
Enhanced API Standards
Ensures consistent API design, documentation, and implementation best practices across PHP, JavaScript, and TypeScript files.
actions:
-
type: enforce conditions:
-
pattern: "@api\s+(?!GET|POST|PUT|DELETE|PATCH|OPTIONS|HEAD)" message: "Use standard HTTP methods (GET, POST, PUT, DELETE, PATCH, OPTIONS, HEAD) for API endpoints."
-
pattern: "function\s+[a-zA-Z]+Api\s*\([^)]\)\s\{[^}]*\}" pattern_negate: "(?s)(throw new \w+Exception|return\s+(?:\d{3}|4\d\d|5\d\d))" message: "Ensure API functions handle or return errors appropriately using exceptions or HTTP status codes."
-
pattern: "(?<!@api\s+)(?<!\s+returns\s+)(?<!\s+throws\s+)[A-Z]{3,}(?!\s+)" message: "HTTP methods should be prefixed with '@api' for documentation purposes."
-
pattern: "\bresponse\b(?![^;]*\.json\()" message: "Ensure all API responses are properly formatted, preferably as JSON."
-
-
type: suggest message: | API Best Practices:
- HTTP Methods: Use proper HTTP methods for operations (GET for retrieval, POST for creation, etc.).
- Status Codes: Use appropriate HTTP status codes to communicate the result of the request.
- Versioning: Implement API versioning to manage changes without breaking existing integrations.
- Documentation:
- Swagger/OpenAPI: Use tools like Swagger for comprehensive API documentation.
- Endpoint Descriptions: Clearly document all endpoints including path, methods, parameters, and possible responses.
- Authentication & Security:
- Implement OAuth, JWT, or similar secure authentication methods.
- Use HTTPS for all API communications.
- Rate Limiting: Implement rate limiting to prevent abuse and ensure fair usage.
- Error Handling:
- Provide clear, human-readable error messages with corresponding status codes.
- Implement error logging for debugging purposes.
- Pagination: For list endpoints, implement pagination to manage large datasets.
- Validation: Validate input data at the API level to ensure data integrity.
- CORS: Configure CORS headers if your API is meant to be consumed by web applications from different domains.
- Monitoring: Set up monitoring for API performance and usage statistics.
metadata: priority: high version: 1.1
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.
- yesterday First seen · 56 lines · 639 tokens per session scan A 86c733441669
api-standards is a cursor rule published in the GitHub repository abderrahimghazali/cursor-rules (2 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 639 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
creating-cursor-rules
Meta-rule for creating effective Cursor IDE rules with best practices, patterns, and examples.
creating-skills
Meta-guide for creating effective Claude Code skills with proper structure, CSO optimization, and real examples.
cursorrules
You are a disciplined senior engineer working with someone who may be a domain expert, not a programmer. Build it correctly and safely, not just fast.
cursorrules
Cursor rule "cursorrules" from BlueBirdBack/godot-cursorrules, covering godot 4.4 game development .cursorrules, core development guidelines, code style, naming conventions and scene organization.
new_feature
You are an expert Product Owner and Technical Lead focused on helping users define and plan new features through collaborative discovery and structured documentation.
new_project
You are an expert Product Owner focused on helping users define new software projects through collaborative vision creation.