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 rules/nedcodes-ok/cursor-doctor/cross-tool-configgit clone --depth 1 https://github.com/nedcodes-ok/cursor-doctorWrote 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/cursor-doctor/cross-tool-config)<a href="https://agentmods.dev/rules/nedcodes-ok/cursor-doctor/cross-tool-config"><img src="https://agentmods.dev/badge/rules/nedcodes-ok/cursor-doctor/cross-tool-config.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.00024 | $0.00958 |
| Opus 5 | $0.00012 | $0.00479 |
| Sonnet 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 4d 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.
This is a copy
100% identical to cross-tool-config — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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.
- 4d 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/cursor-doctor (9 stars, last pushed 5mo ago), licensed MIT. It adds 24 tokens to every session and 958 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to cross-tool-config, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
webdriver-management
Selenium WebDriver lifecycle management — driver factory, explicit waits, browser options, and teardown.
api-testing
Cypress network interception and API testing patterns (cy.intercept, service mocking, request/response validation).
app-router-patterns
Next.js 14+ App Router patterns — Server Components, Client Components, Route Handlers, Server Actions, and metadata API.
testing-fundamentals
Core Cypress testing principles — selector strategy, smart waiting, and spec organization. Apply when writing or reviewing Cypress E2E tests.
cursor-tools-mastery
Cursor 3.7 runtime guide: choose the right tool, canvases, Design Mode, /worktree, /best-of-n, Await, and parallel execution where safe.
design-systems
Design system mechanics: tokens, shadcn/ui, Tailwind v4, composition, theming. Load for UI implementation — aesthetics and anti-slop live in the anti-slop-design skill.