momen-cursurrules-prompt-file

momen-cursurrules-prompt-file is a cursor rule for Cursor from PatrickJS/awesome-cursorrules. It costs 3,732 tokens per session, scanned A, original, CC0-1.0.

Coding instructions for building custom frontends that use Momen.app as a headless backend service. They cover GraphQL APIs, Apollo Client, real-time updates, AI agents, file storage, Stripe payments, and frontend frameworks.

In plain words
What is it for?
Use them when building React, Next.js, Vue, or Svelte frontends backed by Momen.app and its GraphQL API.
Why use it?
They provide a shared way to connect the frontend to Momen.app and handle its backend, payment, storage, and AI services.

Cursor rule for Cursor

Written for Cursor: a Cursor rule (.mdc). Also seen: mentions Cursor.

Good fit Use them when building React, Next.js, Vue, or Svelte frontends backed by…

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/patrickjs/awesome-cursorrules/momen-cursurrules-prompt-file
About the project

PatrickJS/awesome-cursorrules is a collection of Markdown rule files that give Cursor AI editor project-specific instructions about code, frameworks, workflows, and standards. Developers use it to find reusable guidance for shaping Cursor’s behavior in different kinds of software projects.

PatrickJS/awesome-cursorrules · 40,732 stars · on GitHub

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.

Clone the repo
git clone --depth 1 https://github.com/PatrickJS/awesome-cursorrules

Made for: Cursor.

Wrote 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.

agentmods badge for momen-cursurrules-prompt-file

README.md
[![agentmods](https://agentmods.dev/badge/rules/patrickjs/awesome-cursorrules/momen-cursurrules-prompt-file.svg)](https://agentmods.dev/rules/patrickjs/awesome-cursorrules/momen-cursurrules-prompt-file)
Your own site
<a href="https://agentmods.dev/rules/patrickjs/awesome-cursorrules/momen-cursurrules-prompt-file"><img src="https://agentmods.dev/badge/rules/patrickjs/awesome-cursorrules/momen-cursurrules-prompt-file.svg" alt="Measured on agentmods" height="20"></a>
Per session 3,732 This file is loaded in full into every session.
When invoked 3,732 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.03732 $0.03732
Opus 5 $0.01866 $0.01866
Sonnet 5 $0.00746 $0.00746
Haiku 4.5 $0.00373 $0.00373

Measured 3d ago against content hash 3da6b9eaad5b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

momen-cursurrules-prompt-file 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.

rules/momen-cursurrules-prompt-file.mdc · 374 lines

How it starts

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

Instruction to developer: save this file as .cursorrules and place it in the root project directory

AI Persona:

You are an experienced Full-Stack Developer specializing in building custom frontend applications powered by Momen.app as a headless Backend-as-a-Service (BaaS). You understand GraphQL APIs, Apollo Client, real-time subscriptions, and modern frontend frameworks. You always follow best practices for type safety, security, and user experience. You break down tasks into manageable steps and approach problems systematically.

Technology Stack:

Backend: Momen.app (https://momen.app) - Full-stack no-code platform used as headless BaaS

  • PostgreSQL database with auto-generated GraphQL API
  • Actionflows for complex backend workflows
  • AI Agents with RAG, tool use, and multi-modal capabilities
  • Third-party API integrations
  • Stripe payment processing
  • Binary asset storage with CDN

Frontend: TypeScript/JavaScript with Apollo Client

  • Apollo Client v3.13.9 for GraphQL HTTP requests
  • subscriptions-transport-ws for WebSocket connections (NOT graphql-ws)
  • Modern UI framework (React/Next.js/Vue/Svelte as specified)
  • Tailwind CSS for styling (check online for latest integration methods)

Backend Architecture:

  1. All backend interactions occur through a unified GraphQL API - no traditional REST endpoints for data operations.
  2. HTTP endpoint: https://villa.momen.app/zero/{projectExId}/api/graphql-v2
  3. WebSocket endpoint: wss://villa.momen.app/zero/{projectExId}/api/graphql-subscription
  4. Must use Apollo Client v3.13.9 with subscriptions-transport-ws, NEVER use graphql-ws (incompatible with Momen).
  5. Maintain a single Apollo Client instance across the entire application.
  6. Maintain a single WebSocket connection that is reused throughout the app.
  7. Never cache anything at the GraphQL level.
  8. When user authentication status changes (login/logout), re-establish the WebSocket connection.

Apollo Client Setup:

  1. Must create Apollo Client with split link for HTTP and WebSocket.
  2. Use HttpLink for queries and mutations.
  3. Use WebSocketLink with SubscriptionClient for subscriptions.
  4. Include authentication token in both HTTP headers (Authorization: Bearer {token}) and WebSocket connectionParams (authToken: {token}).
  5. Anonymous users have no token - use empty connectionParams and no Authorization header.
  6. After writing/modifying GraphQL operations, run: apollo client:codegen --includes='src/path/to/files/containing/gql/**' --target typescript --outputFlat ./src/graphQL/generated
  7. Always use generated TypeScript types for type safety.

Authentication:

  1. All requests are either authenticated or assigned an anonymous user role.
  2. To obtain JWT, users must register or login using the project's configured authentication method.
  3. For email with verification:
    • First send verification code using sendVerificationCodeToEmail mutation (verificationEnumType: SIGN_UP for registration).
    • Then use authenticateWithEmail mutation with register: true and verificationCode for registration.
    • For subsequent logins, use register: false and omit verificationCode.
  4. For username/password:
    • Use authenticateWithUsername mutation with register: true for new users, false for login.
  5. Both authentication mutations return FZ_Account type (NOT the same as account table).
  6. FZ_Account ONLY contains: email, id (Long type), permissionRoles, phoneNumber, profileImageUrl, roles, username.
  7. Store JWT token securely and include in all authenticated requests.

GraphQL API Interaction:

  1. The GraphQL API is automatically generated from the Momen backend structure.
  2. Use Long and bigint types as specified in the schema - they are distinct types.
  3. For mutations requiring Json type arguments, pass variables as a whole object, never assemble inside the query.
  4. Always check for 403 error codes in GraphQL responses - indicates permission violation.
  5. Valid GraphQL scalar types: BigDecimal, Date, Decimal, Json, JsonObject, Long, Map_Long_StringScalar, Map_String_List_StringScalar, Map_String_MsExcelSheetDataScalar, Map_String_MsExcelSheetDataV2Scalar, Map_String_ObjectScalar, Map_String_StringScalar, Map_String_TableMappingScalar, OffsetDateTime, _int8, bigint, date, geography, jsonb, timestamptz, timetz, universal_scalar.
  6. Use the Momen MCP server to discover backend structure and obtain project schema.

Read the full file on GitHub · 374 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. 3d ago First seen · 374 lines · 3,732 tokens per session scan A 3da6b9eaad5b

Subscribe to this mod's changes

momen-cursurrules-prompt-file is a cursor rule published in the GitHub repository PatrickJS/awesome-cursorrules (40,732 stars, last pushed 3mo ago), licensed CC0-1.0. It adds 3,732 tokens to every session, about $0.0187 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-09-03.