agents-at-scale-ark: Cursor rule for Cursor

.cursorrules

cursorrules is a cursor rule for Cursor from mckinsey/agents-at-scale-ark. It costs 351 tokens per session, scanned A, original, Apache-2.0.

A set of repository rules for writing commit messages and pull-request titles in Conventional Commits format, such as "feat:" or "fix:". It also specifies where work files belong and how pull requests should be structured.

In plain words
What is it for?
Use it when committing code, opening pull requests, or deciding where experimental files and personal notes should go.
Why use it?
It keeps changes consistent and lets automated checks accept or reject commits and pull requests predictably.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/. Also seen: mentions Cursor.

This is mckinsey/agents-at-scale-ark's own configuration. It tells Cursor how to work on agents-at-scale-ark itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything agents-at-scale-ark configures →

Reuse

Borrowing it

Nothing to install: this file belongs to mckinsey/agents-at-scale-ark. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/mckinsey/agents-at-scale-ark/main/.cursorrules
Clone the repo
git clone --depth 1 https://github.com/mckinsey/agents-at-scale-ark

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 cursorrules

README.md
[![agentmods](https://agentmods.dev/badge/rules/mckinsey/agents-at-scale-ark/cursorrules/github.svg)](https://agentmods.dev/rules/mckinsey/agents-at-scale-ark/cursorrules)
Your own site
<a href="https://agentmods.dev/rules/mckinsey/agents-at-scale-ark/cursorrules"><img src="https://agentmods.dev/badge/rules/mckinsey/agents-at-scale-ark/cursorrules/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.

agentmods 80×15 button for cursorrules

Your own site · 80×15
<a href="https://agentmods.dev/rules/mckinsey/agents-at-scale-ark/cursorrules"><img src="https://agentmods.dev/badge/rules/mckinsey/agents-at-scale-ark/cursorrules.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 351 This file is loaded in full into every session.
When invoked 351 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.00351 $0.00351
Opus 5.5 $0.00140 $0.00140
Sonnet 5.5 $0.00070 $0.00070
Haiku 4.5 $0.00035 $0.00035

Measured 2mo ago against content hash e072fda150e8, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

cursorrules 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 2mo 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.

.cursorrules · 45 lines

What it actually says

Cursor Rules for ARK Project

Commit Message Format

MANDATORY: All commit messages and PR titles must follow conventional commit format:

  • feat: new feature
  • fix: bug fix
  • docs: documentation changes
  • chore: maintenance tasks
  • refactor: code refactoring
  • test: adding tests
  • ci: CI/CD changes
  • build: build system changes
  • perf: performance improvements

Examples:

  • feat: add agent deployment workflow
  • fix: resolve memory leak in executor
  • docs: update installation guide

Non-conventional commits will be rejected by automated checks.

Code Style

  • Follow existing patterns in the codebase
  • No comments unless explicitly requested
  • Use absolute paths for file operations
  • Prefer editing existing files over creating new ones

Pull Request Format

When creating pull requests, use this simple format:

## Summary
- Brief description of changes

DO NOT include "Test plan" sections in PR descriptions.

Personal/Experimental Files

MANDATORY: All personal documentation, experimental tests, and working artifacts must be placed in the vibe_artifacts/ directory at the repository root.

  • ✅ Correct: vibe_artifacts/QUERY_DEEP_DIVE.md
  • ✅ Correct: vibe_artifacts/a2a-streaming-error-test/
  • ❌ Incorrect: QUERY_DEEP_DIVE.md (root level)
  • ❌ Incorrect: tests/a2a-streaming-error-test/ (unless it's an official test)

The vibe_artifacts/ folder is gitignored and is intended for personal working documents, experimental code, and temporary artifacts that don't need to be committed to the repository.

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. 2mo ago First seen · 45 lines · 351 tokens per session scan A e072fda150e8

Subscribe to this mod's changes

cursorrules is a cursor rule published in the GitHub repository mckinsey/agents-at-scale-ark (434 stars, last pushed yesterday), licensed Apache-2.0. It adds 351 tokens to every session, about $0.0014 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-09-03.

Related

cursorrules compared with cursor rules from other repositories

cursorrules next to 6 cursor rules from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
cursorrulesmckinsey/agents-at-scale-arkCursor rule434yesterdayApache-2.0A351Cursor
changelogOrlojHQ/orlojCursor rule1267d agoApache-2.0A196Cursor
git-authorRyanAlberts/best-of-Agent-HarnessesCursor rule1.5k3d agoCC-BY-SA-4.0A235Cursor
gitChatbotXIO/ChatbotXCursor rule1.1ktodaynoneA29Cursor
savevictusfate/scaffoldCursor rule72d agoMITA88Cursor
git-commitkyungseo/ai-workflow-harnessCursor rule143mo agoApache-2.0A18Cursor
04-review-and-commitpueraeternis/agentic-project-templateCursor rule24mo agoMITA546Cursor