project_structure

A reference layout for a software project, showing where source code, tests, feature plans, editor settings, continuous-integration workflows, and project documentation belong. Continuous integration means automated checks that run when code changes.

In plain words
What is it for?
Use it to organize a modular project with feature specifications, implementation plans, task lists, source code, tests, and development guidelines.
Why use it?
It gives developers and coding agents a shared map of the project, reducing confusion about where to find or add files.

Cursor rule for Cursor

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.

agentmods
npx agentmods add rules/ezorita/scotpy/project_structure
Clone the repo
git clone --depth 1 https://github.com/ezorita/scotpy

Made for: Cursor.

Per session 275 This file is loaded in full into every session.
When invoked 275 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00275 $0.00275
Opus 5 $0.00138 $0.00138
Sonnet 5 $0.00055 $0.00055
Haiku 4.5 $0.00028 $0.00028

Measured 2d ago against content hash 9644f4752b8c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 2d 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/project_structure.mdc · 27 lines

What it actually says

This is the file structure of the smart coding template:

project-name/
├── .cursor/
│   └── rules/                 # AI-optimized Cursor rules
├── .github/
│   └── workflows/
│       └── ci.yml             # Continuous integration pipeline
├── .vscode/                   # Editor settings and extension recommendations
├── project/                   # Auto-generated project documentation
│   ├── vision.md              # Project vision (created during setup)
│   └── 00_feature-name/       # Feature-specific docs (created per feature)
│       ├── feature.md         # Feature specification and requirements
│       ├── implementation.md  # Technical implementation strategy
│       └── tasks.md           # Detailed task breakdown
├── src/                       # Source code
├── tests/                     # Test suite
├── .pre-commit-config.yaml    # Pre-commit hooks configuration
├── .secrets.baseline          # Known secrets patterns for security scanning
├── CONTRIBUTING.md            # Development and contribution guidelines
├── poetry.toml                # Poetry-specific configuration
├── pyproject.toml             # Project configuration
├── README.md                  # Your project README
└── DOCS.md                    # This document (can be deleted after cloning)
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.

  1. 2d ago First seen · 27 lines · 275 tokens per session scan A 9644f4752b8c

Subscribe to this mod's changes

project_structure is a cursor rule published in the GitHub repository ezorita/scotpy (5 stars, last pushed 1y ago), licensed MIT. It adds 275 tokens to every session, about $0.0014 per session on Opus 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.