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/drumnation/unsplash-smart-mcp-server/agent-use-project-docs.rulesgit clone --depth 1 https://github.com/drumnation/unsplash-smart-mcp-serverWrote 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/drumnation/unsplash-smart-mcp-server/agent-use-project-docs.rules)<a href="https://agentmods.dev/rules/drumnation/unsplash-smart-mcp-server/agent-use-project-docs.rules"><img src="https://agentmods.dev/badge/rules/drumnation/unsplash-smart-mcp-server/agent-use-project-docs.rules.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.1 | $0.00336 | $0.00336 |
| Opus 5 | $0.00168 | $0.00168 |
| Sonnet 5 | $0.00067 | $0.00067 |
| Haiku 4.5 | $0.00034 | $0.00034 |
Grade A, and why
agent-use-project-docs.rules 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 6d 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
Rule: Agent Use of Project Documentation
Purpose
Ensure that agents actively reference existing project documentation during planning, implementation, and debugging. This reinforces architecture decisions, prevents duplication, and leverages prior domain knowledge.
When to Read Docs
Agents MUST consult relevant documentation:
- Before implementing or planning a new feature
- Before debugging a non-trivial issue
- When using or modifying any shared component, service, or utility
- When setting up a new app, package, or configuration
- When unsure about naming, architecture, or design patterns
What to Read
Agents should prioritize:
docs/features/— Feature implementation and rationaledocs/architecture/adr/— Architectural decisionsdocs/concepts/— Core patterns and abstractionsdocs/packages/[name]/— Workspace-specific detailsREADME.md,ONBOARDING.md,CONTRIBUTING.md— Setup and standards
Use index files (*.index.md) to navigate efficiently.
Usage Expectations
- ✅ Reference relevant documents in the plan or task file
- ✅ Reuse prior design decisions and avoid re-debating settled architecture
- ✅ Cross-link helpful docs in responses where appropriate
- ✅ Load related
.mdfiles into memory when working on relevant code - ✅ If unclear, run the
consult-documentation-indexprocess to search
Related Rules
- @project-documentation-structure.rules.mdc
- @feature-task-plan-generator.rules.mdc
- @agent-self-report.rules.mdc
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.
- 6d ago First seen · 54 lines · 336 tokens per session scan A ad0f7e3827c6
agent-use-project-docs.rules is a cursor rule published in the GitHub repository drumnation/unsplash-smart-mcp-server (63 stars, last pushed 7mo ago), licensed MIT. It adds 336 tokens to every session, about $0.0017 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-30.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.