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/nedcodes-ok/cursorrules-collectionWrote 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/nedcodes-ok/cursorrules-collection/cross-tool-config)<a href="https://agentmods.dev/rules/nedcodes-ok/cursorrules-collection/cross-tool-config"><img src="https://agentmods.dev/badge/rules/nedcodes-ok/cursorrules-collection/cross-tool-config/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/nedcodes-ok/cursorrules-collection/cross-tool-config"><img src="https://agentmods.dev/badge/rules/nedcodes-ok/cursorrules-collection/cross-tool-config.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.00024 | $0.00958 |
| Opus 5.5 | $0.00010 | $0.00383 |
| Sonnet 5.5 | $0.00005 | $0.00192 |
| Haiku 4.5 | $0.00002 | $0.00096 |
Grade A, and why
cross-tool-config 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- cross-tool-config — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cross-Tool AI Configuration
Every AI coding tool has its own instruction format. None of them read each other's files. Here's the landscape and what actually transfers.
Config File Reference
| Tool | File(s) | Location | Glob/Scope Support |
|---|---|---|---|
| Cursor | .cursorrules, .cursor/rules/*.mdc |
Project root | Yes (globs, alwaysApply in .mdc frontmatter) |
| Claude Code | CLAUDE.md |
~/.claude/, project root, subdirs |
No (all content loaded every session) |
| OpenAI Codex | AGENTS.md, AGENTS.override.md |
~/.codex/, project root → cwd |
No (concatenated root-to-leaf) |
| GitHub Copilot | .github/copilot-instructions.md, .github/instructions/*.instructions.md, also reads AGENTS.md/CLAUDE.md/GEMINI.md |
.github/ dir |
Yes (applyTo globs in path-specific files) |
| Windsurf | .windsurfrules, .windsurf/rules/*.md, .windsurf/workflows/*.md |
Project root | No (plain markdown, 12K char limit per file) |
| Gemini CLI | GEMINI.md |
~/.gemini/, project root, subdirs (scans down too) |
No (pure markdown) |
What Transfers Between Tools
- Build/test/lint commands — every tool needs to know how to verify its changes. Write these once, copy to each config
- Coding conventions — naming, formatting, patterns. These are language/project decisions, not tool decisions
- Architecture context — project structure, key directories, tech stack. Same information, different files
- "Don't touch" rules — files, directories, or patterns the AI should leave alone
What Doesn't Transfer
- Frontmatter/metadata — Cursor's
alwaysApply,globs,descriptiondon't exist in CLAUDE.md or AGENTS.md. Copilot hasapplyTobut the format is different - File locations —
.cursor/rules/vs.github/instructions/vs.windsurf/rules/are all different paths - Behavioral tuning — each model responds differently to the same instruction. "Be concise" means different things to Claude, GPT, and Gemini
- Workflows — Windsurf's step-by-step workflows have no equivalent in other tools. Cursor has no workflow concept. Claude Code uses slash commands differently
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 · 52 lines · 24 tokens per session scan A 6e9b81cbf002
cross-tool-config is a cursor rule published in the GitHub repository nedcodes-ok/cursorrules-collection (38 stars, last pushed 7mo ago), licensed MIT. It adds 24 tokens to every session and 958 once invoked, about $0.0001 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-30.
Other cursor rules, from other repositories
auto-update-llms-robots-txt
Auto-update llms.txt and robots.txt when pages are created or edited.
10-feature-development
Feature implementation workflow and engineering mindset.
11-template-conventions
Reusable building blocks shipped with this template - use them instead of writing new ones.
12-new-project
Workflow for starting a new app from this template - rebranding, identity, cleanup and first feature.
13-updating-project
Workflow for updating an existing project - dependency and SDK upgrades, migrations, refactors, bug fixes.
01-tech-stack
Android tech stack and project standards.