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/cmnemoi/cursor-rulesWrote 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/cmnemoi/cursor-rules/900-project-specific)<a href="https://agentmods.dev/rules/cmnemoi/cursor-rules/900-project-specific"><img src="https://agentmods.dev/badge/rules/cmnemoi/cursor-rules/900-project-specific/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/cmnemoi/cursor-rules/900-project-specific"><img src="https://agentmods.dev/badge/rules/cmnemoi/cursor-rules/900-project-specific.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.00738 |
| Opus 5.5 | $0.00000 | $0.00295 |
| Sonnet 5.5 | $0.00000 | $0.00148 |
| Haiku 4.5 | $0.00000 | $0.00074 |
Grade A, and why
900-project-specific 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 1mo 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project-Specific Rules Template
1.0.0
Context
- This file is used as specification only for this project
Recommendation
Languages
- For code and logs: English
- For labels: English language in UI and errors
Overall Architecture
- Project structure: Monorepo with API (PHP/Symfony) and App (Vue.js frontend)
- Architectural patterns used: Domain-Driven Design, Clean Architecture, Command and Query Segregation, and in-memory object repositories for testing
Authentication
- Authentication mechanisms used: JWT Authentication with Lexik JWT Bundle
- External authentication: Integration with Eternaltwin OAuth
State Management
- State management approach: Vuex
- Organization of stores: Feature-based stores
API and Services
- Backend structure: Domain-first organization with bounded contexts in separate folders
- API conventions: RESTful API with API Platform
Testing
- Testing strategy: Unit tests first with in-memory repositories, functional tests when needed
- Testing frameworks: Codeception for backend, Vitest for frontend
- Test patterns: Given-When-Then and test doubles using in-memory repositories
Custom for this project
Backend (PHP/Symfony)
Domain Organization
- The codebase is organized by domain bounded contexts (Action, Alert, Chat, Communications, Daedalus, Disease, Equipment, Game, Hunter, etc.)
- Each domain has its own set of entities, repositories, services, and interfaces following DDD principles
Testing
- Unit tests use in-memory repositories and service implementations
- Functional tests use Codeception
- Tests follow the Given-When-Then pattern with descriptive method names
Controllers
- API controllers handle HTTP requests and return responses
- Controllers interact with application services that encapsulate domain logic
Frontend (Vue.js)
Structure
- Vue 3 with TypeScript
- Phaser for game-related functionality
- Vue Router for navigation
- Vuex for state management
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.
- 1mo ago First seen · 100 lines · 738 tokens per session scan A 71ca37ff426a
900-project-specific is a cursor rule published in the GitHub repository cmnemoi/cursor-rules (2 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 738 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
vue-typescript-patterns
A set of coding rules for Vue 3 projects using TypeScript, a language that adds type checking to JavaScript. It covers component structure, file locations, TypeScript usage, and Pinia, a library for shared application state.
svelte-5-vs-svelte-4-cursorrules-prompt-file
Cursor rules for comparing Svelte 5 and Svelte 4 development.
sveltekit-typescript-guide-cursorrules-prompt-file
Cursor rules for SvelteKit development with TypeScript integration.
svelte-mcp-tools
Instructions for using the Svelte MCP server tools for documentation lookup, code analysis, and validation.
frontend-rules
A frontend development rule that points to existing Vue pages and components as examples. It refers to chat, notebook, and button files in the project.
frontend
You are an expert in TypeScript, Node.js, Vite, Vue.js, Vue Router, Pinia, VueUse, Ant Design Vue, and UnoCSS, with a deep understanding of best practices and performance optimization techniques in these technologies.