doc-everything-init

A one-time setup rule for adding the doc-everything workflow to a Cursor project. Cursor is a code editor with built-in agent features, and this rule configures its Stop hook and documentation folders.

In plain words
What is it for?
Use it when adopting doc-everything in a repository. It installs the hook, creates the documentation index, and adds project configuration only when the defaults do not fit.
Why use it?
It removes the manual work of connecting the reminder script and creating the initial feature-documentation structure. It also helps adjust watched source and documentation paths when a project uses a different layout.

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/rafaelszago/doc-everything/doc-everything-init
Clone the repo
git clone --depth 1 https://github.com/rafaelszago/doc-everything

Made for: Cursor.

Per session 83 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 987 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.00083 $0.00987
Opus 5 $0.00042 $0.00494
Sonnet 5 $0.00017 $0.00197
Haiku 4.5 $0.00008 $0.00099

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

Security

Grade A, and why

doc-everything-init 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/doc-everything-init.mdc · 91 lines

How it starts

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

Initialize doc-everything for this project (Cursor)

One-time setup so the docs-sync stop hook and the document-feature-* rules work in this repo. The hook works out of the box with sensible defaults — you only need a config file if the defaults don't match this project's layout.

Steps

  1. Install the stop hook.

    • Make sure the hook script is present in the repo and executable — copy hooks/docs-sync.sh from doc-everything and run chmod +x hooks/docs-sync.sh.

    • Create .cursor/hooks.json pointing at it (path relative to the repo root):

      {
        "version": 1,
        "hooks": {
          "stop": [
            { "command": "./hooks/docs-sync.sh" }
          ]
        }
      }
      
    • To enable it across all your projects instead, put the same stop entry in ~/.cursor/hooks.json with an absolute path to the script.

  2. Inspect the repo layout. Find where source lives and what extensions are used (e.g. src/, app/, lib/, packages/*, or a language-specific root), and where documentation should live.

  3. Decide if the defaults fit. The hook watches common source roots (src|app|lib|pkg|internal|cmd|packages) across many languages, excludes tests/vendored/generated code, and expects docs under docs/features/. If that already matches this repo, skip the config file — less to maintain.

  4. Only if needed, write .cursor/doc-everything.json (or .claude/doc-everything.json) at the repo root with the keys that differ from the defaults:

    {
      "docsPath": "docs/features/",
      "srcGlob": "(^|[ /])(src|app)/[^[:space:]]+\\.(ts|tsx)($|[^[:alnum:]])",
      "srcExclude": "(\\.(test|spec)\\.|/__tests__/|/node_modules/)",
      "reason": "Source changed but nothing under {DOCS_PATH} did — document the feature."
    }
    
    • srcGlob / srcExclude are extended regexes matched against git status --porcelain lines. Escape backslashes for JSON (\\.).
    • docsPath must end with a trailing slash.
    • reason is optional; {DOCS_PATH} in it is substituted at runtime.
    • Any omitted key falls back to the built-in default.
    • Alternatively, these map to env vars DOC_EVERYTHING_SRC_GLOB, DOC_EVERYTHING_SRC_EXCLUDE, DOC_EVERYTHING_DOCS_PATH, DOC_EVERYTHING_REASON.

Read the full file on GitHub · 91 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. 2d ago First seen · 91 lines · 83 tokens per session scan A 9942ce4021a1

Subscribe to this mod's changes

doc-everything-init is a cursor rule published in the GitHub repository rafaelszago/doc-everything (2 stars, last pushed 1mo ago), licensed MIT. It adds 83 tokens to every session and 987 once invoked, about $0.0004 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.