directory-listing

A set of rules for viewing files and folders on Unix-like systems such as macOS and Linux, and on Windows.

In plain words
What is it for?
It guides commands for listing files, showing hidden items, sorting results, finding files by name, and finding directories.
Why use it?
It makes directory exploration more consistent and helps avoid noisy folders such as Git metadata and installed dependencies.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/mitas/cursor-rules/directory-listing
Clone the repo
git clone --depth 1 https://github.com/mitas/cursor-rules

Made for: Cursor.

Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,447 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00015 $0.02447
Opus 5 $0.00008 $0.01223
Sonnet 5 $0.00003 $0.00489
Haiku 4.5 $0.00002 $0.00245

Measured yesterday against content hash 0c4cc8eeeaf9, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

directory-listing 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 yesterday.

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.

.cursor/rules/directory-listing.mdc · 238 lines

How it starts

The opening of the file, as written. The whole thing — 238 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Directory Listing Guidelines

Context

  • This rule provides guidance on how to list directory contents on different operating systems.
  • Apply when user asks for directory listing or file exploration.
  • Use when navigating the filesystem.
  • Always consider excluding common large/noisy directories like .git, node_modules, etc.
  • The approach differs between Unix-like systems (Linux, macOS) and Windows systems.

Unix/Linux/macOS Systems

  • Unix systems typically use bash, zsh, or other POSIX-compliant shells.
  • macOS has BSD variants of some commands with slightly different options.

Critical rules for Unix-like systems

  • Use ls for basic directory listing.
  • Use ls -l for detailed listing with permissions, sizes, and dates.
  • Use ls -la to include hidden files (those starting with .).
  • Use ls -lh for human-readable file sizes (KB, MB, GB).
  • Use ls -lt to sort by modification time (newest first).
  • Use ls -lS to sort by file size (largest first).
  • Use find . -type f -name "*.txt" to search for files by pattern.
  • Use find . -type d -name "*src*" to search for directories by pattern.
  • Use find . -type f -exec ls -lh {} \; to get detailed listing of found files.
  • Use du -sh * to show disk usage of directories in human-readable format.
  • Use du -sh */ | sort -hr to show directories sorted by size (largest first).
  • For tree-like view, use the tree command if available or install it.
  • For finding files by content, use grep -r "search-term" ..
  • For file counting, use find . -type f | wc -l.
  • For macOS/BSD systems, remember options may differ slightly from GNU versions.
  • Use the more modern fd command instead of find when available for better performance and simpler syntax.
  • For searching file content with pattern context, use grep -r "search-term" . -A 2 -B 2 to show 2 lines before and after.
  • For large directories, use ls -la | head -20 to limit output to first 20 entries.
  • Consider using exa or lsd as modern replacements for ls when available.

Read the full file on GitHub · 238 lines

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.

  1. yesterday First seen · 238 lines · 15 tokens per session scan A 0c4cc8eeeaf9

Subscribe to this mod's changes

directory-listing is a cursor rule published in the GitHub repository mitas/cursor-rules (2 stars, last pushed 1y ago), licensed MIT. It adds 15 tokens to every session and 2,447 once invoked, about $0.0001 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.