What is naming-standards?

A set of naming rules for investigation files, directories, templates, and technical terms. It defines patterns for making names descriptive, consistent, concise, and free of secrets.

Use it when naming rule files, connector and workflow files, investigation workspaces, templates, and related terminology.

It prevents confusing or inconsistent names that make files and workspaces harder to find and maintain.

naming-standards — Cursor rule for Cursor by sfc-gh-cconner

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/sfc-gh-cconner/support-rules-mcp

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/sfc-gh-cconner/support-rules-mcp/naming-standards.svg)](https://agentmods.dev/rules/sfc-gh-cconner/support-rules-mcp/naming-standards)

Your own site

<a href="https://agentmods.dev/rules/sfc-gh-cconner/support-rules-mcp/naming-standards"><img src="https://agentmods.dev/badge/rules/sfc-gh-cconner/support-rules-mcp/naming-standards.svg" alt="Measured on agentmods" height="20"></a>

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

When invoked 1,868 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.01868	$0.01868
Opus 5	$0.00934	$0.00934
Sonnet 5	$0.00374	$0.00374
Haiku 4.5	$0.00187	$0.00187

Measured 6d ago against content hash a3e8db7fcbf0, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

naming-standards 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 6d 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.

rules/workflows/naming-standards.mdc · 333 lines

How it starts

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

Naming Standards & Conventions

PURPOSE: Consistent naming conventions for rules, templates, files, and terminology.

🎯 Core Principles

Be Descriptive: Names should clearly indicate purpose
Be Consistent: Follow established patterns
Be Concise: Avoid unnecessary verbosity
No Secrets: Never include credentials or sensitive data in names

📁 Rule File Naming

Pattern

{number}-{descriptive-name}.mdc

Examples

✅ Good:
01-github-mcp.mdc
06-snowflake-cli.mdc
08-mono-repo-mcp.mdc

❌ Bad:
github.mdc (no number, less discoverable)
1-mcp.mdc (not descriptive)
github_mcp_integration.mdc (underscore instead of dash)

Numbering

Core rules: 01-14 (numbered for ordering)
Connector rules: Alphabetical, no numbers (python.mdc, jdbc.mdc)
SPCS rules: Alphabetical, no numbers (snowctl.mdc, architecture.mdc)
Workflow rules: Descriptive names (reproductions-templates.mdc)

📂 Directory Naming

Investigation Workspaces

Preferred: tickets/
Avoid: cases/ (for workspace/path references)

# ✅ Good - Uses "tickets" for workspace
tickets/12345678/investigation.md
tickets/SNOW-98765/queries.sql
cp -r templates/spcs tickets/12345678/

# ❌ Bad - Uses "cases" for workspace
cases/12345678/investigation.md

Allowed "Case" Usage

"Customer cases" - General support vernacular ✅
"Use cases" - Pattern/scenario context ✅
"Test cases" - Testing terminology ✅

Template Directories

templates/{category}/{issue-name}/

Examples:

templates/spcs/external-connectivity/
templates/streamlit/session-state/
templates/nativeapps/versioning/
templates/tasks/task-failure/

🏷️ Object Naming in Reproductions

Database Objects

-- Pattern: repro_{category}_{description}

✅ Good:
CREATE DATABASE repro_spcs_db;
CREATE SCHEMA repro_spcs_db.connectivity;
CREATE WAREHOUSE repro_spcs_wh;
CREATE TABLE repro_test_data;

❌ Bad:
CREATE DATABASE MY_TEST_DB;  -- Not parameterized
CREATE DATABASE TICKET_12345;  -- Includes ticket number
CREATE WAREHOUSE LARGE_WH;  -- Not descriptive

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

6d ago First seen · 333 lines · 1,868 tokens per session scan A a3e8db7fcbf0

Subscribe to this mod's changes

naming-standards is a cursor rule published in the GitHub repository sfc-gh-cconner/support-rules-mcp (0 stars, last pushed 11mo ago), licensed Apache-2.0. It adds 1,868 tokens to every session, about $0.0093 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.

naming-standards