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/onurhan1337/rushWrote 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/onurhan1337/rush/ruler_cursor_instructions)<a href="https://agentmods.dev/rules/onurhan1337/rush/ruler_cursor_instructions"><img src="https://agentmods.dev/badge/rules/onurhan1337/rush/ruler_cursor_instructions/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/onurhan1337/rush/ruler_cursor_instructions"><img src="https://agentmods.dev/badge/rules/onurhan1337/rush/ruler_cursor_instructions.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.01895 | $0.01895 |
| Opus 5.5 | $0.00758 | $0.00758 |
| Sonnet 5.5 | $0.00379 | $0.00379 |
| Haiku 4.5 | $0.00189 | $0.00189 |
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 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 — 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-clientwith 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:
- Use the "ikas" MCP list tool to find the correct query/mutation name.
- Use the "ikas" MCP introspect tool to get the operation's full shape (variables, return fields, enums).
- Only after confirming via list + introspect, add the document to
graphql-requests.tsand run codegen.
- For ikas GraphQL specifically, follow this order before any implementation:
GraphQL and API Workflow
- Define queries/mutations in
src/lib/ikas-client/graphql-requests.tsusinggql. - Run
pnpm codegento regeneratesrc/lib/ikas-client/generated/graphql.tstypes and client wrappers. - Acquire a client with
getIkas(token)fromsrc/helpers/api-helpers.ts. - Execute queries via
ikasClient.queries.<name>()and mutations viaikasClient.mutations.<name>(variables).
Enforcement
- Do NOT write inline GraphQL strings inside API routes or components.
- Always import documents from
graphql-requests.tsand runpnpm codegenbefore 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.
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 · 165 lines · 1,895 tokens per session scan A ca67d87f45b3
ruler_cursor_instructions is a cursor rule published in the GitHub repository onurhan1337/rush (5 stars, last pushed 18d ago), licensed MIT. It adds 1,895 tokens to every session, about $0.0076 per session on Opus 5.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.
Other cursor rules, from other repositories
data-table-filters
Install and wire up data-table-filters — filterable React data tables with server-side filtering, faceted counts, infinite scroll, and virtualization, delivered as shadcn registry blocks.
payload-configuration
Shipkit conditionally initializes Payload CMS based on environment variables. The src/payload.config.ts file handles graceful degradation when no database is configured.
supabase-bootstrap
Guidelines for writing Next.js apps with Supabase Auth.
graceful-degradation
Shipkit implements graceful degradation to provide a seamless experience whether users have a database configured or not. When no DATABASEURL is provided, the application automatically falls back to local storage for data persistence.
server-actions-patterns
❌ Never export classes from "use server" files.
supabase-edge
Coding rules for Supabase Edge Functions.