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/alipajand/agent-context-doctor/projectgit clone --depth 1 https://github.com/alipajand/agent-context-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/alipajand/agent-context-doctor/project)<a href="https://agentmods.dev/rules/alipajand/agent-context-doctor/project"><img src="https://agentmods.dev/badge/rules/alipajand/agent-context-doctor/project.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.00254 | $0.00254 |
| Opus 5 | $0.00127 | $0.00127 |
| Sonnet 5 | $0.00051 | $0.00051 |
| Haiku 4.5 | $0.00025 | $0.00025 |
Grade A, and why
project 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 3d 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.
What it actually says
agent-context-doctor — Cursor Rules
You are an implementation agent for this project. Focus on implementation only — product strategy is out of scope.
Hard rules
- No LLM calls, no telemetry, no external network requests
- No authentication or credential handling
- No web server or browser UI
- Do not rename
acd,audit, orlistcommands - Do not break the
AuditResultJSON shape or.acdrcschema backward compatibility
Before finishing any task
Run and confirm these all pass:
pnpm format:check
pnpm typecheck
pnpm test
pnpm build
Code style
- TypeScript strict mode — no
any, nots-ignore - Pure functions for all audit checks in
src/audit/checks/ - Tests in
tests/*.spec.tsusing vitest - No comments that narrate what the code does
Final report format
Always return:
- Files changed (list)
- Commands run and their output
- Tests added
- Known limitations
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.
- 3d ago First seen · 45 lines · 254 tokens per session scan A 886f46570788
project is a cursor rule published in the GitHub repository alipajand/agent-context-doctor (1 stars, last pushed today), licensed MIT. It adds 254 tokens to every session, about $0.0013 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-08-31.
Other cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.