What is scripts-naming?

A set of naming rules for package scripts, Makefile commands, and files in scripts folders. It defines allowed formats, words, environments, and lifecycle names.

Use it when creating or renaming npm or Bun scripts, Make targets, or TypeScript and shell files under scripts directories.

It prevents similar commands and files from being named inconsistently. That makes project tasks easier to find and reduces confusion when adding or renaming them.

scripts-naming — Cursor rule for Cursor by docs-plus/docs.plus

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.

Clone the repo

git clone --depth 1 https://github.com/docs-plus/docs.plus

Made for: Cursor.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/rules/docs-plus/docs.plus/scripts-naming/github.svg)](https://agentmods.dev/rules/docs-plus/docs.plus/scripts-naming)

Your own site

<a href="https://agentmods.dev/rules/docs-plus/docs.plus/scripts-naming"><img src="https://agentmods.dev/badge/rules/docs-plus/docs.plus/scripts-naming/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.

Your own site · 80×15

<a href="https://agentmods.dev/rules/docs-plus/docs.plus/scripts-naming"><img src="https://agentmods.dev/badge/rules/docs-plus/docs.plus/scripts-naming.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 1,354 This file is loaded in full into every session.

When invoked 1,354 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.01354	$0.01354
Opus 5.5	$0.00542	$0.00542
Sonnet 5.5	$0.00271	$0.00271
Haiku 4.5	$0.00135	$0.00135

Measured 1mo ago against content hash e16d79e6595d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

scripts-naming 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.

.cursor/rules/scripts-naming.mdc · 62 lines

How it starts

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

Scripts Naming Convention

Authoritative source: .cursor/docs/scripts-naming-convention.md. Read it before adding or renaming a script, Make target, or file under scripts/.

Grammar

npm/Bun script keys: <verb> | <verb>:<axis> | <verb>:<scope>:<modifier> | <tool>:<sub> | pre<verb> / post<verb>.
Make targets: <verb> | <verb>-<env>-<scope>-<modifier> | <scope>-<verb> (only for grouped families: infra-* verb members, swarm-* run-mode members). Kebab-case, no colons.
Script files in scripts/ and packages/<pkg>/scripts/: kebab-case, verb-first when action-oriented, .ts for new scripts, .sh only when shell is genuinely required, .mjs only for JS-tooling configs.

Closed vocabularies

Modifiers: :fix, :ci, :watch, :coverage, :dry.
Environments: :prod, :stage, :dev.
Scopes: :unit, :e2e, :webapp, :admin, :backend, :rest, :ws, :worker, :styles, :family, :screenshots, :nested-to-flat.
Lifecycle hooks: prepare, postinstall, pretest, prepack, prepublishOnly, plus generic pre<verb>/post<verb> over the reserved verb list. Do not invent new ones (no prebuild, postlint).

Banned

Suffixes: :all, :full, :everything, :complete, :local.
Verbs: validate (use check or <verb>:ci), serve (use start), watch as a bare verb (use <verb>:watch), audit, compile (use build), all.
Filename traps in scripts/: validate-*, *-emergency*, fix-production-*, temp-*, quick-*, wip-*, final-*, v2-*, date prefixes, author prefixes. These are exactly the names that filled scripts/archive/.

Documented exceptions and corner cases

@docs.plus/hocuspocus has no bare dev (service trio: dev:rest / dev:ws / dev:worker).
Webapp start runtime asymmetry: bare start runs Node; start:prod / start:stage run Bun.
migrate:nested-to-flat[:dry] — kebab-cased migration scope + closed-vocab dry modifier.
Single-tool wrapper workspaces (e.g. @docs.plus/supabase_back) use bare verbs; the workspace name encodes the tool prefix.
Husky hook filenames (pre-commit.sh, pre-push.sh, commit-msg.sh, post-merge.sh) and npm-lifecycle script files (prepack.ts, preflight.ts) keep their upstream-mandated names.
Make's env axis includes local (e.g. make dev-local) — legitimate, not subject to the npm-side :local ban.
swarm-* is a grouped Make family whose members are document-swarm run modes (swarm-demo, swarm-stress), not verbs — mirrors the @docs.plus/document-swarm run --mode CLI.

Read the full file on GitHub · 62 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.

1mo ago First seen · 62 lines · 1,354 tokens per session scan A e16d79e6595d

Subscribe to this mod's changes

scripts-naming is a cursor rule published in the GitHub repository docs-plus/docs.plus (95 stars, last pushed yesterday), licensed MIT. It adds 1,354 tokens to every session, about $0.0054 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-30.

Collaboration collaborative-framework collaborative-research collaborative-writing document docx

rule-generating-agent

This rule is essential for maintaining consistency and quality in rule creation across the codebase. It must be followed whenever: (1) A user requests a new rule to be created, (2) An existing rule needs modification, (3) The user asks to remember certain behaviors or patterns, or (4) Future behavior changes are…

appboypov/pew-pew-cli · 1,197 tokens

ts-dependency-management-agent

Apply when adding, removing, or managing dependencies, or when structuring code modules in a TypeScript project, especially for CLIs. Promotes minimizing external dependencies, using lockfiles (package-lock.json), vetting dependencies, following SOLID principles for modular code, and using dependency injection for…

appboypov/pew-pew-cli · 62 tokens

npm-cli-packaging-agent

Apply when preparing a TypeScript CLI tool for distribution via npm, specifically when configuring package.json, handling executables, and considering cross-platform compatibility. Covers the bin field, shebang line (#!/usr/bin/env node), pre-publish checks, installation instructions, and Node engine compatibility.

appboypov/pew-pew-cli · 61 tokens

scripts-naming