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/donvito/ai-backendsWrote 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/donvito/ai-backends/coding-standards)<a href="https://agentmods.dev/rules/donvito/ai-backends/coding-standards"><img src="https://agentmods.dev/badge/rules/donvito/ai-backends/coding-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.
<a href="https://agentmods.dev/rules/donvito/ai-backends/coding-standards"><img src="https://agentmods.dev/badge/rules/donvito/ai-backends/coding-standards.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.00374 | $0.00374 |
| Opus 5.5 | $0.00150 | $0.00150 |
| Sonnet 5.5 | $0.00075 | $0.00075 |
| Haiku 4.5 | $0.00037 | $0.00037 |
Grade A, and why
coding-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.
What it actually says
Coding Standards
This document outlines coding standards and best practices for the AI Backends project.
TypeScript Usage
- Use proper TypeScript types and avoid
anywhen possible - Create interfaces for complex data structures
- Use type guards when necessary for type narrowing
- Leverage TypeScript's utility types (Pick, Omit, Partial, etc.)
API Design
- Follow RESTful principles for resource-based endpoints
- Use consistent naming conventions for endpoints
- Document APIs using OpenAPI/Swagger via Hono's built-in support
- Return appropriate HTTP status codes
- Implement proper error handling and validation
- Routes should be in the src/routes folder and named with dash-separated lowercase words
Error Handling
- Use consistent error handling patterns
- Provide meaningful error messages
- Create custom error classes when appropriate
- Log errors with sufficient context for debugging
- Don't expose sensitive information in error messages
Performance Considerations
- Avoid blocking operations when possible
- Use caching where appropriate
- Consider rate limiting for resource-intensive operations
- Implement pagination for large data sets
- Implement exponential backoff for all external API calls to avoid hitting rate limits
Security Best Practices
- Sanitize and validate all user input
- Store sensitive information in environment variables
- Implement proper authentication and authorization
- Follow the principle of least privilege
- Keep dependencies updated
AI Integration
- Handle AI model responses appropriately
- Set reasonable timeouts for AI model calls
- Implement fallbacks for when AI services are unavailable
- Consider streaming responses for long-running AI operations
- Validate AI output before returning to clients
- Implement exponential backoff for all external API calls to avoid hitting rate limits
- Use the reusable AI service layer when connecting from API routes
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 · 59 lines · 374 tokens per session scan A b3d0aa36eda3
coding-standards is a cursor rule published in the GitHub repository donvito/ai-backends (146 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 374 tokens to every session, about $0.0015 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-30.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).