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/ddebixx/frontend-templateWrote 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/ddebixx/frontend-template/project-structure)<a href="https://agentmods.dev/rules/ddebixx/frontend-template/project-structure"><img src="https://agentmods.dev/badge/rules/ddebixx/frontend-template/project-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/ddebixx/frontend-template/project-structure"><img src="https://agentmods.dev/badge/rules/ddebixx/frontend-template/project-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.00000 | $0.00344 |
| Opus 5.5 | $0.00000 | $0.00138 |
| Sonnet 5.5 | $0.00000 | $0.00069 |
| Haiku 4.5 | $0.00000 | $0.00034 |
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 3d 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.
What it actually says
Project structure
- shadcn UI →
src/components/ui/(primitives only) - Domain presentational UI →
src/components/[domain]/ - Shared UI (≥2 domains) →
src/components/shared/ - Feature modules →
src/features/[domain]/(same*.types.ts/*.constants.tslayout as components; compose UI and wire hooks, fetchers, and Next.js server actions) - HTTP + Zod →
src/fetchers/[domain]/ - Tanstack Query hooks →
src/hooks/[domain]/(usable from components and features) - Context + app-wide providers →
src/providers/(compose inAppProviders) - shadcn
cn→src/lib/utils.ts - Locale config →
src/i18n/; catalogs →src/messages/ - Global utils/types/constants →
src/utils,src/types,src/constants(utilsusable from components and features) - E2E →
e2e/[domain]/[path].spec.ts - Next.js routes →
src/app/; Vite screens →src/pages/
Do not call Tanstack Query or fetch directly from components. Go through hooks / fetchers, usually via a feature.
Details: docs/frontend/conventions/PROJECT_STRUCTURE.md
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.
- 3d ago Changed · +1 lines 0f667e319fda
- 1mo ago First seen · 24 lines · 0 tokens per session scan A 0a1f6c327b01
project-structure is a cursor rule published in the GitHub repository ddebixx/frontend-template (5 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 344 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-08-31.
Other cursor rules, from other repositories
windsurfrules
Create detailed components with these requirements.
state-management
Use the following stack. Do not introduce or recommend Redux or React Context for shared/global state.
backend
Backend development rules for TT Studio - AI model management backend.
tanstack-start-guide
TanStack Start best practices emphasizing client-first architecture, type safety, and modern React patterns.
new-component
Workflow for creating new React components.
tanstack-react-router_routing
TanStack Router: Routing.