Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/hatefsystems/search-engine-corenpx agentmods add rules/hatefsystems/search-engine-core/documentation-organizationWrote 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/hatefsystems/search-engine-core/documentation-organization)<a href="https://agentmods.dev/rules/hatefsystems/search-engine-core/documentation-organization"><img src="https://agentmods.dev/badge/rules/hatefsystems/search-engine-core/documentation-organization/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/hatefsystems/search-engine-core/documentation-organization"><img src="https://agentmods.dev/badge/rules/hatefsystems/search-engine-core/documentation-organization.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.02795 | $0.02795 |
| Opus 5.5 | $0.01118 | $0.01118 |
| Sonnet 5.5 | $0.00559 | $0.00559 |
| Haiku 4.5 | $0.00280 | $0.00280 |
Grade A, and why
documentation-organization 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.
How it starts
The opening of the file, as written. The whole thing — 460 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Organization Standards
Documentation Location Rules
Rule: NO Markdown Files in Project Root (Except README.md)
CRITICAL: Only README.md should exist in the project root directory. All other markdown files MUST be organized in the docs/ directory structure.
✅ ALLOWED in root:
- README.md (main project documentation)
❌ FORBIDDEN in root:
- Any other .md files
- Implementation summaries
- Test results
- Feature documentation
- Architecture docs
Documentation Directory Structure
docs/
├── api/ # API endpoint documentation
├── features/ # Feature guides and overviews
├── implementation/ # Implementation summaries for major features
├── testing/ # Test results and verification reports
├── architecture/ # System architecture and design documents
├── privacy/ # Privacy architecture and compliance
├── guides/ # User guides and tutorials
├── development/ # Development setup and guidelines
├── troubleshooting/ # Common issues and solutions
└── archive/ # Historical/deprecated documentation
File Placement Guidelines
API Documentation → docs/api/
When: Documenting API endpoints, request/response formats, authentication
Files:
{feature}_endpoint.md- API reference for endpoints{FEATURE}_QUICK_START.md- Getting started guidesREADME.md- API documentation index
Example:
docs/api/profile_endpoint.md
docs/api/link_blocks_endpoint.md
docs/api/LINK_BLOCKS_QUICK_START.md
Feature Overviews → docs/features/
When: High-level feature documentation for users and developers
Content:
- Feature overview and purpose
- User-facing capabilities
- Use cases and examples
- Configuration options
- Future enhancements
Example:
docs/features/LINK_BLOCKS.md
docs/features/SEARCH_FILTERS.md
Implementation Summaries → docs/implementation/
When: Completing major features (3+ days of work), architectural changes
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 · 460 lines · 2,795 tokens per session scan A a94dc80eb56b
documentation-organization is a cursor rule published in the GitHub repository hatefsystems/search-engine-core (5 stars, last pushed today), licensed Apache-2.0. It adds 2,795 tokens to every session, about $0.0112 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-31.
Other cursor rules, from other repositories
documentation
Documentation module guidelines for Infinispan docs.
infinispan
Infinispan project guidelines for coding and reviews.
cli
CLI module specific guidelines.
query
Query module specific guidelines.
agents
../../AGENTS.md.
qb-linq-headers
qb-linq implementation headers — CRTP, out-of-line locations, safe patterns.