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/maccman/ai-monorepo-scaffoldWrote 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/maccman/ai-monorepo-scaffold/monorepo-structure)<a href="https://agentmods.dev/rules/maccman/ai-monorepo-scaffold/monorepo-structure"><img src="https://agentmods.dev/badge/rules/maccman/ai-monorepo-scaffold/monorepo-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/maccman/ai-monorepo-scaffold/monorepo-structure"><img src="https://agentmods.dev/badge/rules/maccman/ai-monorepo-scaffold/monorepo-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.00695 | $0.00695 |
| Opus 5 | $0.00347 | $0.00347 |
| Sonnet 5 | $0.00139 | $0.00139 |
| Haiku 4.5 | $0.00069 | $0.00069 |
Grade A, and why
monorepo-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 10d 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Monorepo Structure - Critical Rules
NEVER PUT BUSINESS LOGIC IN apps/web/src/lib/
VIOLATION EXAMPLE (DO NOT DO THIS):
// ❌ WRONG: apps/web/src/lib/crawler.ts
export async function crawlWebsite() {
// Database operations, AI calls, etc.
}
CORRECT APPROACH:
// ✅ CORRECT: packages/api/src/actions/crawling/worker.ts
export async function crawlSingleWebsite() {
// Business logic belongs here
}
// ✅ CORRECT: apps/web/src/pages/api/crawl.ts (thin wrapper only)
import { crawlSingleWebsite } from '@app/api'
export const POST: APIRoute = async ({ request }) => {
const result = await crawlSingleWebsite(params)
return new Response(JSON.stringify(result))
}
Directory Rules
packages/api/src/ - Business Logic ONLY
packages/api/src/
├── actions/ # ✅ All business logic here
│ ├── crawling/ # ✅ Crawling operations
│ ├── extraction/ # ✅ AI/data processing
│ ├── browser/ # ✅ External service clients
│ └── seeding/ # ✅ Database seeding
├── routers/ # ✅ tRPC API routes
├── schemas/ # ✅ Zod validation schemas
└── index.ts # ✅ Export everything for apps
apps/web/src/ - Frontend + Thin API Wrappers ONLY
apps/web/src/
├── components/ # ✅ React UI components only
├── hooks/ # ✅ Frontend React hooks only
├── pages/api/ # ✅ Thin API wrappers only (no business logic)
├── client/ # ✅ tRPC client setup only
├── lib/utils.ts # ✅ Frontend utilities only
└── server/ # ✅ Astro server config only
MANDATORY PATTERNS
1. Business Logic → packages/api
- Database operations
- AI/ML processing
- External API clients (Browserless, OpenAI, GCS)
- Data transformation
- Validation schemas
- Complex algorithms
2. API Routes → Thin Wrappers Only
// ✅ CORRECT: Thin wrapper pattern
export const POST: APIRoute = async ({ request }) => {
// 1. Auth validation only
// 2. Parse request with Zod
// 3. Call packages/api function
// 4. Return response
}
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.
- 10d ago First seen · 107 lines · 695 tokens per session scan A 586fa8d4c740
monorepo-structure is a cursor rule published in the GitHub repository maccman/ai-monorepo-scaffold (304 stars, last pushed 10mo ago), licensed MIT. It adds 695 tokens to every session, about $0.0035 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
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.
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.