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.
npx agentmods add instructions/onurhan1337/rush/agents-mdgit clone --depth 1 https://github.com/onurhan1337/rushWhat 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 | $0.01962 | $0.01962 |
| Opus 5 | $0.00981 | $0.00981 |
| Sonnet 5 | $0.00392 | $0.00392 |
| Haiku 4.5 | $0.00196 | $0.00196 |
Grade A, and why
rush AGENTS.md 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 2d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- rush CLAUDE.md — 97% identical, 7 lines differ
How it starts
The opening of the file, as written. The whole thing — 163 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.
Adding New API Requests (Procedure)
- Discover operation via MCP: run ikas list to locate the operation, then ikas introspect to confirm its schema.
- Add your GraphQL query/mutation to
src/lib/ikas-client/graphql-requests.tsusing thegqltag. - Run
pnpm codegento generate types and update the generated client. - Use
getIkasto create the ikas client inside API routes or server actions. - For a query, call
ikasClient.queries.<YourQuery>(); for a mutation, callikasClient.mutations.<YourMutation>(variables).
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.
- 2d ago First seen · 163 lines · 1,962 tokens per session scan A fdb338505e7a
rush AGENTS.md is an instructions file published in the GitHub repository onurhan1337/rush (5 stars, last pushed 15d ago), licensed MIT. It adds 1,962 tokens to every session, about $0.0098 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.
Other instructions, from other repositories
data-table-filters AGENTS.md
Instructions for openstatusHQ/data-table-filters, covering agents.md, a. using data-table-filters in someone's project, install recipes, things that bite and b. contributing to this repository.
data-table-filters CLAUDE.md
Instructions for openstatusHQ/data-table-filters, covering claude.md, project overview, monorepo structure (pnpm + turborepo), key commands and database.
coss AGENTS.md
AGENTS.md instructions for cosscom/coss, covering agents.md and main documentation.
ui-beats CLAUDE.md
Instructions for nikhils4/ui-beats, a project described as: Animated React components you own. 55 components built with TypeScript, Tailwind CSS and Motion. Copy, paste, or install with the shadcn CLI.
magicui AGENTS.md
Instructions for magicuidesign/magicui, covering project context, key principles, before writing code, rules and accessibility (a11y).
kan AGENTS.md
AGENTS.md instructions for kanbn/kan, covering agents.md, project overview, setup commands, project structure and code style.