naming-stuff

A set of rules for choosing clear names for files, functions, URLs, variables, and other code elements. It treats names as documentation that should show purpose and context.

In plain words
What is it for?
Use it when naming new models, database tables, functions, classes, API endpoints, background jobs, features, components, and important variables.
Why use it?
Good names make code easier to understand and reduce the need to search elsewhere for an explanation. The rules also encourage care before choosing names that will be difficult to change later.

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/technickai/claude_telemetry/naming-stuff
Clone the repo
git clone --depth 1 https://github.com/TechNickAI/claude_telemetry

Made for: Cursor.

Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 276 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.00011 $0.00276
Opus 5 $0.00005 $0.00138
Sonnet 5 $0.00002 $0.00055
Haiku 4.5 $0.00001 $0.00028

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

Security

Grade A, and why

naming-stuff 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/naming-stuff.mdc · 43 lines

What it actually says

Naming Conventions

When in doubt, take time to name things well. It's one of the hardest problems in computer science.

Importance

  • Names are a form of documentation that never goes out of date
  • Good names reduce cognitive load and make code self-documenting
  • Names should reveal intent and provide context
  • Time spent on naming is an investment in future understanding

When to Pause and Consider Naming Carefully

The more permanent/harder to change, the more time to spend on naming:

  • Creating new models or database tables
  • Defining core functions or classes
  • Establishing API endpoints or URLs
  • Naming background jobs or tasks
  • Creating new features or components
  • Defining key variables that appear throughout codebase

Notably, don't spend excessive time on naming for simple things that are easy to change.

When Names Aren't Obvious

When a name for a new file, function, class, etc. isn't immediately obvious:

  • Pause and ask what we should name it. It's better to ask than to guess and have to rename later.
  • Consider multiple alternatives
  • Evaluate options based on:
    • Clarity and intuitiveness
    • Technical accuracy
    • Future flexibility
    • Project context
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 · 43 lines · 11 tokens per session scan A 0a8eeb6c460e

Subscribe to this mod's changes

naming-stuff is a cursor rule published in the GitHub repository TechNickAI/claude_telemetry (30 stars, last pushed 10mo ago), licensed MIT. It adds 11 tokens to every session and 276 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-30.