ruler_cursor_instructions

A set of project rules for building a Next.js web app that uses the ikas online-store administration API through GraphQL. It tells the coding agent how to discover API operations, generate types, and follow the project's coding conventions.

In plain words
What is it for?
Building store features, creating interface components, and adding ikas GraphQL queries or mutations with generated TypeScript types.
Why use it?
It prevents the agent from guessing API names or data shapes and helps avoid exposing secrets or adding code that conflicts with the 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/onurhan1337/rush/ruler_cursor_instructions
Clone the repo
git clone --depth 1 https://github.com/onurhan1337/rush

Made for: Cursor.

Per session 1,895 This file is loaded in full into every session.
When invoked 1,895 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.01895 $0.01895
Opus 5 $0.00948 $0.00948
Sonnet 5 $0.00379 $0.00379
Haiku 4.5 $0.00189 $0.00189

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

Security

Grade A, and why

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

.cursor/rules/ruler_cursor_instructions.mdc · 165 lines

How it starts

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

Project Rules for Ikas App Starter App (Next.js)

Core Principles

  • Prefer simplicity, readability, explicitness. Keep logic in small, testable functions.
  • TypeScript strict; avoid any. Use precise types from generated GraphQL.
  • Treat API tokens and secrets as sensitive; never log them.

Stack Overview

  • Next.js 15 App Router, React 19, TypeScript, Tailwind + shadcn/ui.
  • ikas Admin GraphQL via @ikas/admin-api-client with codegen.
  • Session via iron-session.

MCP Usage

  • When generating new UI components, use the "shadcn" MCP to fetch component boilerplates and demos. Align with existing src/components/ui/* structure.
  • When generating or exploring ikas GraphQL operations, use the "ikas" MCP list and introspect tools to discover available queries/mutations and their shapes before implementation.
    • For ikas GraphQL specifically, follow this order before any implementation:
      1. Use the "ikas" MCP list tool to find the correct query/mutation name.
      2. Use the "ikas" MCP introspect tool to get the operation's full shape (variables, return fields, enums).
      3. Only after confirming via list + introspect, add the document to graphql-requests.ts and run codegen.

GraphQL and API Workflow

  • Define queries/mutations in src/lib/ikas-client/graphql-requests.ts using gql.
  • Run pnpm codegen to regenerate src/lib/ikas-client/generated/graphql.ts types and client wrappers.
  • Acquire a client with getIkas(token) from src/helpers/api-helpers.ts.
  • Execute queries via ikasClient.queries.<name>() and mutations via ikasClient.mutations.<name>(variables).

Enforcement

  • Do NOT write inline GraphQL strings inside API routes or components.
  • Always import documents from graphql-requests.ts and run pnpm codegen before usage.
  • Always call ikas operations through ikasClient.queries|mutations.<operation>() to keep type-safety.
  • Before adding a new operation, first run the ikas MCP list tool, then introspect to confirm details.

Read the full file on GitHub · 165 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 · 165 lines · 1,895 tokens per session scan A ca67d87f45b3

Subscribe to this mod's changes

ruler_cursor_instructions is a cursor rule published in the GitHub repository onurhan1337/rush (5 stars, last pushed 15d ago), licensed MIT. It adds 1,895 tokens to every session, about $0.0095 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-31.