project-structure

Architecture and project-organization rules for Agentset, an open-source platform that helps applications search information and generate answers from it. The code is a monorepo, meaning one repository contains several related applications and shared packages.

In plain words
What is it for?
Use them when adding or changing applications and packages, managing workspace dependencies with Bun, or deciding where database, search, email, storage, billing, and shared UI code should live.
Why use it?
They make it clear where the web app, database, search engine, background jobs, storage, payments, and shared code belong, reducing inconsistent project structure.

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/agentset-ai/agentset/project-structure
Clone the repo
git clone --depth 1 https://github.com/agentset-ai/agentset

Made for: Cursor.

Per session 1,215 This file is loaded in full into every session.
When invoked 1,215 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.01215 $0.01215
Opus 5 $0.00607 $0.00607
Sonnet 5 $0.00243 $0.00243
Haiku 4.5 $0.00121 $0.00121

Measured 2d ago against content hash ccd8789d4223, 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 · 190 lines

How it starts

The opening of the file, as written. The whole thing — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Project Structure & Monorepo Guidelines

Overview

Agentset is a Turborepo monorepo containing a Next.js web app and supporting packages. This is an open-source RAG (Retrieval-Augmented Generation) platform built with modern web technologies.

Monorepo Structure

Core Applications

  • apps/web/ - Main Next.js application with App Router

Internal Packages (Workspace Dependencies)

  • packages/db/ - Database schema, Prisma client, and types
  • packages/demo/ - Demo data and templates
  • packages/emails/ - Email templates and components (using react-email and resend)
  • packages/engine/ - RAG engine with vector stores and embeddings
  • packages/jobs/ - Background job definitions (Trigger.dev)
  • packages/storage/ - File storage utilities (S3)
  • packages/stripe/ - Payment processing utilities
  • packages/tinybird/ - Data warehousing and analytics (Tinybird)
  • packages/ui/ - Shared UI components (Shadcn-based)
  • packages/utils/ - Shared utility functions
  • packages/validation/ - Shared Zod schemas
  • packages/webhooks/ - Webhook definitions and handlers
  • tooling/ - Development and build tooling

Package Management

Use Bun with Workspace Protocol

  • Use bun as the package manager (required by packageManager field)
  • Reference internal packages with workspace:* in package.json
  • Use catalog: references for shared external dependencies
{
  "dependencies": {
    "@agentset/db": "workspace:*",
    "@agentset/ui": "workspace:*",
    "typescript": "catalog:"
  }
}

Workspace Scripts

  • bun dev - Start all services in watch mode
  • bun dev:web - Start web app with dependencies
  • bun build - Build all packages
  • bun lint - Run linting across workspace
  • bun typecheck - Type check all packages

Directory Naming Conventions

Use Kebab-Case for Directories

  • Directory names should use lowercase with dashes: auth-wizard/, api-client/
  • File names should use kebab-case: auth-provider.tsx, user-settings.ts
  • Avoid camelCase or PascalCase for directories

Read the full file on GitHub · 190 lines

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 · 190 lines · 1,215 tokens per session scan A ccd8789d4223

Subscribe to this mod's changes

project-structure is a cursor rule published in the GitHub repository agentset-ai/agentset (2,079 stars, last pushed 1mo ago), licensed MIT. It adds 1,215 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.