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/mhmdreza-rafiei/agent-toolsnpx agentmods add rules/mhmdreza-rafiei/agent-tools/files-folders-structureWrote 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/mhmdreza-rafiei/agent-tools/files-folders-structure)<a href="https://agentmods.dev/rules/mhmdreza-rafiei/agent-tools/files-folders-structure"><img src="https://agentmods.dev/badge/rules/mhmdreza-rafiei/agent-tools/files-folders-structure/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/mhmdreza-rafiei/agent-tools/files-folders-structure"><img src="https://agentmods.dev/badge/rules/mhmdreza-rafiei/agent-tools/files-folders-structure.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.01135 | $0.01135 |
| Opus 5 | $0.00567 | $0.00567 |
| Sonnet 5 | $0.00227 | $0.00227 |
| Haiku 4.5 | $0.00113 | $0.00113 |
Grade A, and why
files-folders-structure 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 9d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Files and folders (naming & structure)
Applies to new paths and when auditing the tree. Pair with migration for renames/moves (update refs, verify, then remove old).
Skip for chat-only help with no file changes.
Folders
- Lowercase only.
- Prefer one word (
test,core,errors,users). - Max two words when one word is not enough (
api_gateway, not three-word names). - Use nesting for meaning instead of long folder names:
test/errors/user/nottest_errors_user/.
Files (code & config stems)
- snake_case, lowercase:
email.py,api_call.py. - The stem (name without extension) must not:
- Repeat the parent folder name — as its own
_segment, plural/singular (tests/test), or glued into another segment (core/+coreapi_*becausecoreapistarts withcore). - Embed a language or format token (
py,ts,yaml,json, …) as if it were the extension. - Duplicate a word (
core_coreapi,user_user_call).
- Repeat the parent folder name — as its own
| Bad | Why | Good (same folder) |
|---|---|---|
actions/github_action.py |
folder name in file | actions/github.py |
tests/test_sql.py |
folder name in file | tests/sql.py |
errors/page_not_found_error.yaml |
folder name in file | errors/page_not_found.yaml |
core/py_api_call.py |
format token in stem | core/api_call.py |
core/core_coreapi_call.py |
folder + duplicate | core/api_call.py |
core/coreapi_call.py |
glued folder token (core inside coreapi) |
core/api_call.py |
users/user_user_call.py |
duplicate word | users/call.py |
If the only distinct part left is one word, use that: tests/sql.py, actions/github.py.
Tooling-mandated names (e.g. Dockerfile, Makefile, go.mod) stay as required by the ecosystem; everything else follows this rule.
Documentation files
- Root / well-known agent docs: UPPERCASE stem —
README.md,AGENTS.md,CLAUDE.md,DESIGN.md,CHANGELOG.md,LICENSE, etc. - Other documentation (under
docs/,context/, …): lowercase snake or single-word stems —context/standards.md,docs/setup_guide.md.
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.
- 9d ago First seen · 113 lines · 1,135 tokens per session scan A 930c29e391ea
files-folders-structure is a cursor rule published in the GitHub repository mhmdreza-rafiei/agent-tools (5 stars, last pushed 22d ago), licensed MIT. It adds 1,135 tokens to every session, about $0.0057 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
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-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.