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/mitas/cursor-rulesWrote 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/mitas/cursor-rules/directory-listing)<a href="https://agentmods.dev/rules/mitas/cursor-rules/directory-listing"><img src="https://agentmods.dev/badge/rules/mitas/cursor-rules/directory-listing/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/mitas/cursor-rules/directory-listing"><img src="https://agentmods.dev/badge/rules/mitas/cursor-rules/directory-listing.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.00015 | $0.02447 |
| Opus 5.5 | $0.00006 | $0.00979 |
| Sonnet 5.5 | $0.00003 | $0.00489 |
| Haiku 4.5 | $0.00002 | $0.00245 |
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 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 — 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
lsfor basic directory listing. - Use
ls -lfor detailed listing with permissions, sizes, and dates. - Use
ls -lato include hidden files (those starting with .). - Use
ls -lhfor human-readable file sizes (KB, MB, GB). - Use
ls -ltto sort by modification time (newest first). - Use
ls -lSto 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 -hrto show directories sorted by size (largest first). - For tree-like view, use the
treecommand 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
fdcommand instead offindwhen available for better performance and simpler syntax. - For searching file content with pattern context, use
grep -r "search-term" . -A 2 -B 2to show 2 lines before and after. - For large directories, use
ls -la | head -20to limit output to first 20 entries. - Consider using
exaorlsdas modern replacements forlswhen available.
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 · 238 lines · 15 tokens per session scan A 0c4cc8eeeaf9
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.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.
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.
shared-plane-packages
Pattern for creating shared plane packages that serve both migration and runtime planes.