Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/girijashankarj/cursor-handbooknpx agentmods add rules/girijashankarj/cursor-handbook/code-organizationWrote 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/girijashankarj/cursor-handbook/code-organization)<a href="https://agentmods.dev/rules/girijashankarj/cursor-handbook/code-organization"><img src="https://agentmods.dev/badge/rules/girijashankarj/cursor-handbook/code-organization/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/girijashankarj/cursor-handbook/code-organization"><img src="https://agentmods.dev/badge/rules/girijashankarj/cursor-handbook/code-organization.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.00000 | $0.00861 |
| Opus 5.5 | $0.00000 | $0.00344 |
| Sonnet 5.5 | $0.00000 | $0.00172 |
| Haiku 4.5 | $0.00000 | $0.00086 |
Grade A, and why
code-organization 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Organization Rules
Project Structure
{{CONFIG.paths.source}}/
├── {{CONFIG.paths.apiPath}}/
│ ├── {{CONFIG.folderNames.common}}/ # Shared API utilities
│ │ ├── errors/ # Error classes
│ │ ├── middleware/ # Shared middleware
│ │ ├── {{CONFIG.folderNames.types}}/ # Shared type definitions
│ │ ├── validators/ # Shared validators
│ │ └── logger.ts # Logging utility
│ └── handlers/
│ └── v1/ # Versioned handlers
│ ├── {entity}/
│ │ ├── create/
│ │ ├── read/
│ │ ├── update/
│ │ └── list/
├── {{CONFIG.paths.eventsPath}}/ # Event handlers
├── {{CONFIG.folderNames.services}}/ # Business services
├── {{CONFIG.folderNames.models}}/ # Data models
└── config/ # Configuration
Naming Conventions
Files
| Type | Pattern | Example |
|---|---|---|
| Handler | kebab-case |
create-order.ts |
| Service | kebab-case.service |
order.service.ts |
| Model | kebab-case.model |
order.model.ts |
| Type | kebab-case.types |
order.types.ts |
| Test | kebab-case.test |
order.service.test.ts |
| Constants | kebab-case.constants |
order.constants.ts |
| Utility | kebab-case.util |
date.util.ts |
| Middleware | kebab-case.middleware |
auth.middleware.ts |
Code
| Type | Convention | Example |
|---|---|---|
| Variables | camelCase | orderTotal |
| Functions | camelCase | calculateTotal() |
| Classes | PascalCase | OrderService |
| Interfaces | PascalCase with I prefix (optional) | OrderInput or IOrderInput |
| Constants | UPPER_SNAKE_CASE | MAX_RETRY_COUNT |
| Enums | PascalCase | OrderStatus |
| Database columns | snake_case | created_at |
Import Rules
- External packages first (alphabetical)
- Internal packages (
{{CONFIG.packages.internalPrefix}}/...) second - Relative imports last (parent → sibling → child)
- Blank line between each group
- No circular dependencies
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 · 93 lines · 0 tokens per session scan A 3e69962ffa38
code-organization is a cursor rule published in the GitHub repository girijashankarj/cursor-handbook (33 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 861 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-09-03.
Other cursor rules, from other repositories
data-fetching
Data fetching patterns with TanStack Query, Server Components, and Supabase.
full-stack-ship-discipline
Require frontend changes and their DB/RPC/RLS/storage/secret dependencies to ship and be remotely verified together. Apply when implementing code that reads or writes backend state. Do not apply to plan- or present-then-stop audits; production data mutation still requires confirmation.
supabase
Supabase patterns and conventions for this project.
senior-engineer
Senior-engineer execution defaults for the Next.js + React + Supabase stack — state/data library choices, separation of concerns, security non-negotiables. Attach when building or refactoring features in a React/Next.js/Supabase codebase.
composer-fullstack-delivery
New screen, feature, endpoint, or multi-layer slice — freeze seams, ship one demoable path, failure modes, Run/Wired handoff. Skip for a single-module code change.
rules
A set of project rules for deploying a separated frontend and backend in Docker containers, with shared code, AI services, response formats, and server settings. Docker is software for packaging and running applications in isolated containers.