docs-directory

A set of repository rules for documentation layout and filenames. Documentation folders must be named docs, and documentation files must use uppercase names with hyphens.

In plain words
What is it for?
Use it when adding documentation directories or files, such as GETTING-STARTED.md or CONTRIBUTING.md.
Why use it?
It keeps documentation in a predictable location and naming style so contributors can find and recognize it consistently.

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/langwatch/better-agents/docs-directory
Clone the repo
git clone --depth 1 https://github.com/langwatch/better-agents

Made for: Cursor.

Per session 6 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 86 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.00006 $0.00086
Opus 5 $0.00003 $0.00043
Sonnet 5 $0.00001 $0.00017
Haiku 4.5 $0.00001 $0.00009

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

Security

Grade A, and why

docs-directory 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 2d 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.

.cursor/rules/docs-directory.mdc · 9 lines

What it actually says

DIRECTIVES:

  • Documentation directories should be named "docs" (lowercase)
  • Documentation files should use CAPITAL LETTERS with hyphens (e.g., GETTING-STARTED.md, CONTRIBUTING.md)
  • This follows the convention of treating documentation as a special top-level concern
  • Apply this to any new documentation directories created in the project
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. 2d ago First seen · 9 lines · 6 tokens per session scan A 0ae1972e521b

Subscribe to this mod's changes

docs-directory is a cursor rule published in the GitHub repository langwatch/better-agents (1,552 stars, last pushed 3mo ago), licensed MIT. It adds 6 tokens to every session and 86 once invoked, about $0.0000 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-30.