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/johnpolacek/vibecode.party.starter/101-project-structuregit clone --depth 1 https://github.com/johnpolacek/vibecode.party.starterWrote 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/johnpolacek/vibecode.party.starter/101-project-structure)<a href="https://agentmods.dev/rules/johnpolacek/vibecode.party.starter/101-project-structure"><img src="https://agentmods.dev/badge/rules/johnpolacek/vibecode.party.starter/101-project-structure.svg" alt="Measured on agentmods" 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 | $0.01212 | $0.01212 |
| Opus 5 | $0.00606 | $0.00606 |
| Sonnet 5 | $0.00242 | $0.00242 |
| Haiku 4.5 | $0.00121 | $0.00121 |
Grade A, and why
101-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 4d 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 — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Structure Guidelines
Follow these guidelines when creating new files to maintain consistent project organization.
Directory Structure
├── app/ # Next.js app router pages and API routes
│ ├── api/ # API routes
│ ├── _actions/ # Server actions (private)
│ ├── actions/ # Server actions (public)
│ ├── [route]/ # Route directories
│ │ ├── page.tsx # Page component
│ │ ├── layout.tsx # Layout component
│ │ └── components/ # Route-specific components
├── components/ # Shared UI components
│ ├── ui/ # Basic UI components
│ └── [feature]/ # Feature-specific components
├── convex/ # Convex schema, functions, and backend logic
├── lib/ # Utility functions and services
│ ├── services/ # Business logic and data services (Convex client wrappers)
│ ├── validations/ # Form and data validation
│ ├── convex/ # Convex client configuration and utilities
│ └── config/ # Configuration files
├── types/ # TypeScript type definitions
└── public/ # Static assets
File Location Guidelines
-
Components
- Reusable UI components →
/components/ui/ - Feature-specific shared components →
/components/[feature]/ - Route-specific components →
/app/[route]/components/
- Reusable UI components →
-
Business Logic
- Convex backend logic →
/convex/ - Database services (Convex client wrappers) →
/lib/services/ - Utility functions →
/lib/utils.ts - Type definitions →
/types/ - Form validation →
/lib/validations/ - Convex client config →
/lib/convex/
- Convex backend logic →
-
Server Actions
- Private actions →
/app/_actions/ - Public actions →
/app/actions/
- Private actions →
-
API Routes
- All API routes →
/app/api/
- All API routes →
Naming Conventions
- Files
- React components and Utilities: kebab-case (e.g.,
auth-utils.ts) - Pages:
page.tsx - Layouts:
layout.tsx - Server actions: kebab-case (e.g.,
create-sponsor.ts) - Convex functions: kebab-case (e.g.,
record-visit.ts)
- React components and Utilities: kebab-case (e.g.,
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.
- 4d ago First seen · 155 lines · 1,212 tokens per session scan A 54191b49c261
101-project-structure is a cursor rule published in the GitHub repository johnpolacek/vibecode.party.starter (27 stars, last pushed 1y ago), licensed MIT. It adds 1,212 tokens to every session, about $0.0061 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-30.
Other cursor rules, from other repositories
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.
cli-error-handling
CLI command error handling patterns.
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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.