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/barisercan/cursorrulesWrote 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/barisercan/cursorrules/core-files-documentation)<a href="https://agentmods.dev/rules/barisercan/cursorrules/core-files-documentation"><img src="https://agentmods.dev/badge/rules/barisercan/cursorrules/core-files-documentation/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/barisercan/cursorrules/core-files-documentation"><img src="https://agentmods.dev/badge/rules/barisercan/cursorrules/core-files-documentation.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.00629 | $0.00629 |
| Opus 5.5 | $0.00252 | $0.00252 |
| Sonnet 5.5 | $0.00126 | $0.00126 |
| Haiku 4.5 | $0.00063 | $0.00063 |
Grade A, and why
core-files-documentation 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.
What it actually says
description: Maintain core files documentation in memory-bank for easy codebase navigation globs: "**/*" alwaysApply: true
Core Files Documentation Rule
Automatically maintain documentation of core source files in memory-bank/coreFiles.md.
actions:
-
type: enforce message: | CORE FILES DOCUMENTATION PROTOCOL
REQUIRED: Update
memory-bank/coreFiles.mdwhen core source files changeTARGET FILES: All .py files under src/ EXCEPT:
- main.py files
- init.py files
- Test files (tests/ directory)
DOCUMENTATION FORMAT:
## path/to/filename.py **Description**: Brief explanation of file purpose **Classes**: - ClassName (line X): What this class does - AnotherClass (line Y): Purpose and responsibility **Notable Methods**: - method_name() (line Z): Key functionality description - important_method() (line W): What it accomplishes **Important Notes**: - Key implementation details - Performance characteristics - API patterns or special behaviors - Known limitations or warningsUPDATE TRIGGERS:
- New core file created under src/
- Existing core file modified (classes/methods added/changed)
- User requests "update core files" or similar
- Significant refactoring or architectural changes
MAINTENANCE RULES:
- Keep documentation under 20 lines per file
- Focus on classes, key methods, and important notes
- Include line numbers for easy navigation
- Update when file structure changes significantly
- Remove entries when files are deleted
examples:
-
input: "New file: src/trading/strategy_engine.py" output: "Add documentation entry to memory-bank/coreFiles.md"
-
input: "Modified: src/market_data_collector/binance/rest/symbol_fetcher.py" output: "Update existing entry with new classes/methods"
-
input: "update core files documentation" output: "Review all src/ files and update coreFiles.md"
metadata: priority: high version: 1.0 enforcement: automatic dependencies: ["memory-bank"]
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 · 86 lines · 629 tokens per session scan A e7a6c3b166fe
core-files-documentation is a cursor rule published in the GitHub repository barisercan/cursorrules (35 stars, last pushed 1y ago), licensed MIT. It adds 629 tokens to every session, about $0.0025 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
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.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).