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/claude-mdgit 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/claude-md)<a href="https://agentmods.dev/rules/nedcodes-ok/cursor-doctor/claude-md"><img src="https://agentmods.dev/badge/rules/nedcodes-ok/cursor-doctor/claude-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.00000 | $0.00812 |
| Opus 5 | $0.00000 | $0.00406 |
| Sonnet 5 | $0.00000 | $0.00162 |
| Haiku 4.5 | $0.00000 | $0.00081 |
Grade A, and why
claude-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 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 claude-md — 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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md Rules
CLAUDE.md is loaded into every Claude Code session. It's your one chance to onboard the model to your codebase before each conversation.
What Goes In CLAUDE.md
- WHAT: tech stack, project structure, key directories. In monorepos, list the apps, shared packages, and what each one does. Claude doesn't explore on its own until prompted
- WHY: purpose of the project, what the different parts do, business context that affects technical decisions ("we use polling instead of websockets because our infra doesn't support persistent connections")
- HOW: build commands, test commands, lint commands, deploy process. If your project uses
pnpminstead ofnpm, say so here or Claude will guess wrong
Discovery Hierarchy
~/.claude/CLAUDE.md— global, applies to every projectCLAUDE.mdat project root — project-specific, overrides globalCLAUDE.mdin subdirectories — more specific, stacks with parent files- Claude concatenates all found files, root to leaf. Later files override earlier ones for conflicting guidance
What Makes CLAUDE.md Get Ignored
- Claude Code wraps CLAUDE.md with a system reminder saying "this context may or may not be relevant to your tasks." If your file is full of situational hotfixes and edge cases, Claude is more likely to skip the whole thing
- Keep instructions broadly applicable to tasks you'll run. "Always run tests after changes" stays relevant. "When modifying the payment webhook handler, remember the Stripe API changed in v2024-06" only matters for one specific task
- Shorter, focused files get followed more reliably than 2000-line dumps. If you hit diminishing returns, split into subdirectory CLAUDE.md files
Patterns That Work
- Build/test/lint commands at the top — these are universally relevant and anchor the file as useful context
- Project map with directory descriptions:
src/api/does X,src/workers/does Y,shared/contains Z - Explicit tool preferences: package manager, test runner, formatter, deployment method
- Coding conventions that differ from defaults: "we use tabs not spaces," "we use Zustand not Redux," "error responses use Problem Details format"
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 · 46 lines · 0 tokens per session scan A f5579870eca7
claude-md is a cursor rule published in the GitHub repository nedcodes-ok/cursor-doctor (9 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 812 tokens. A static security scan graded it A with 0 findings. It is 100% identical to claude-md, 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.