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/ivangrynenko/cursorrules/agents-mdgit clone --depth 1 https://github.com/ivangrynenko/cursorrulesWrote 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/instructions/ivangrynenko/cursorrules/agents-md)<a href="https://agentmods.dev/instructions/ivangrynenko/cursorrules/agents-md"><img src="https://agentmods.dev/badge/instructions/ivangrynenko/cursorrules/agents-md.svg" alt="Measured on agentmods" 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 | $0.02432 | $0.02432 |
| Opus 5 | $0.01216 | $0.01216 |
| Sonnet 5 | $0.00486 | $0.00486 |
| Haiku 4.5 | $0.00243 | $0.00243 |
Grade A, and why
cursorrules 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 yesterday.
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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cursor Agents Guide (Using Cursor Rules)
This document explains how to use the rules in this repository with Cursor and serves as a single entry point that references the existing rule files. It avoids duplication by linking directly to the .cursor/rules/*.mdc sources.
If you installed these rules via the installer, a project‑local AGENTS.md can be generated that lists only the rules you chose. By default, the installer writes AGENTS.md if absent; it overwrites only when you pass --yes.
How To Use With Cursor
- Open your project in Cursor. Rules under
.cursor/rulesare discovered automatically by Cursor. - Keep this AGENTS.md handy as your quick index to the rule set.
- For installation methods and advanced options, see
README.md.
Installation Options
For full installation details and examples, see README.md.
- Core rules only:
--core - Web stack (includes core):
--web-stackor--ws - Python (includes core):
--python - JavaScript security (includes core):
--javascript - All rules:
--all - Tag-based selection:
--tags "<expression>"or--tag-preset <name> - Ignore files control:
--ignore-files yes|no|ask
Tag taxonomy is documented in TAG_STANDARDS.md.
Rule Bundles (Source of Truth)
Below are the rule bundles and their rule files. Each item links directly to the authoritative file under .cursor/rules/.
Core
- .cursor/rules/cursor-rules.mdc
- .cursor/rules/git-commit-standards.mdc
- .cursor/rules/github-actions-standards.mdc
- .cursor/rules/improve-cursorrules-efficiency.mdc
- .cursor/rules/pull-request-changelist-instructions.mdc
- .cursor/rules/readme-maintenance-standards.mdc
- .cursor/rules/testing-guidelines.mdc
- .cursor/rules/confluence-editing-standards.mdc
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.
- yesterday First seen · 127 lines · 2,432 tokens per session scan A 574daacd0046
cursorrules AGENTS.md is an instructions file published in the GitHub repository ivangrynenko/cursorrules (88 stars, last pushed 10mo ago), licensed MIT. It adds 2,432 tokens to every session, about $0.0122 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.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).