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/project-structure)<a href="https://agentmods.dev/rules/donvito/ai-backends/project-structure"><img src="https://agentmods.dev/badge/rules/donvito/ai-backends/project-structure/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/project-structure"><img src="https://agentmods.dev/badge/rules/donvito/ai-backends/project-structure.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.00521 | $0.00521 |
| Opus 5.5 | $0.00208 | $0.00208 |
| Sonnet 5.5 | $0.00104 | $0.00104 |
| Haiku 4.5 | $0.00052 | $0.00052 |
Grade A, and why
project-structure 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.
How it starts
The opening of the file, as written. The whole thing — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Backends Project Structure
This document outlines the recommended folder structure for the AI Backends project.
Main Structure
The main entry point is src/index.ts, which initializes the application.
ai-backend/
├── src/ # Source code
│ ├── config/ # App configuration, env vars
│ ├── controllers/ # Route controllers (handle request/response)
│ ├── middlewares/ # Express middlewares
│ ├── models/ # Data models
│ ├── routes/ # Route definitions
│ ├── services/ # Business logic
│ ├── utils/ # Utility functions
│ ├── schemas/ # Validation schemas
│ └── index.ts # App entry point
├── tests/ # Test files
│ ├── unit/
│ ├── integration/
│ └── fixtures/ # Test data
├── dist/ # Compiled output
├── docs/ # Documentation
└── scripts/ # Utility scripts
Key Directories
src/routes/
Contains route definitions for the application's API endpoints. Examples include:
- routes/keywords.ts - Keyword extraction endpoint
- routes/summarize.ts - Text summarization endpoint
- routes/describeImage.ts - Image description endpoint
src/schemas/
Contains validation schemas for request and response data.
src/services/
Contains business logic and external API interactions.
- services/ai.ts - AI service layer
- services/ollama.ts - Ollama service layer
- services/openai.ts - OpenAI service layer
- services/anthropic.ts - Anthropic service layer
- services/openrouter.ts - OpenRouter service layer
src/utils/
Contains utility functions used throughout the application.
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 · 64 lines · 521 tokens per session scan A 22dfdd00a6cf
project-structure is a cursor rule published in the GitHub repository donvito/ai-backends (146 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 521 tokens to every session, about $0.0021 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).