14-security-secrets

14-security-secrets is a cursor rule for Cursor from sfc-gh-cconner/support-rules-mcp. It costs 1,961 tokens per session, scanned A, original, Apache-2.0.

A set of rules for keeping passwords, keys, tokens, connection strings, and personal information out of code and documentation.

In plain words
What is it for?
Use it when writing rules, examples, configurations, or documentation that handle secrets or sensitive information.
Why use it?
It reduces the risk of exposing credentials or sensitive data in repositories, examples, logs, and investigation results.

Cursor rule for Cursor

Written for Cursor: a Cursor rule (.mdc).

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/sfc-gh-cconner/support-rules-mcp/14-security-secrets
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.

agentmods badge for 14-security-secrets

README.md
[![agentmods](https://agentmods.dev/badge/rules/sfc-gh-cconner/support-rules-mcp/14-security-secrets.svg)](https://agentmods.dev/rules/sfc-gh-cconner/support-rules-mcp/14-security-secrets)
Your own site
<a href="https://agentmods.dev/rules/sfc-gh-cconner/support-rules-mcp/14-security-secrets"><img src="https://agentmods.dev/badge/rules/sfc-gh-cconner/support-rules-mcp/14-security-secrets.svg" alt="Measured on agentmods" height="20"></a>
Per session 1,961 This file is loaded in full into every session.
When invoked 1,961 The same file — it is already loaded in full.
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.1 $0.01961 $0.01961
Opus 5 $0.00981 $0.00981
Sonnet 5 $0.00392 $0.00392
Haiku 4.5 $0.00196 $0.00196

Measured 5d ago against content hash 413b3b835dc0, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

14-security-secrets 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 5d 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/core/14-security-secrets.mdc · 287 lines

How it starts

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

Security & Secrets Handling

PURPOSE: Security and secrets hygiene for rules, examples, and documentation.

🔐 Principles

  • Never commit secrets (keys, tokens, passwords, connection strings) to the repository
  • Prefer environment variables or secret managers; avoid inline credentials
  • Minimize data exposure in logs and outputs; redact sensitive fields consistently
  • Use least privilege and time-bounded credentials for investigations
  • Use placeholders in all examples and documentation

✅ Do

  • Store secrets in environment variables or secure secret stores
  • Parameterize credentials and account-specific values in examples
  • Provide .example or .template files instead of real secrets
  • Validate that examples omit or mask PII/credentials
  • Use placeholders: <account_id>, <user_name>, <password>

❌ Don't

  • Don't check in .env files with real values
  • Don't embed tokens in examples, configs, or documentation
  • Don't echo secrets in outputs
  • Don't use real account locators or identifiers in examples
  • Don't include customer-specific information

🎯 Placeholder Standards

Use These Placeholders

# Good examples with placeholders
<account_locator>    # For account identifiers
<deployment>         # For deployment names (prod3, azeastus2prod)
<account_id>         # For numeric account IDs
<user_name>          # For usernames
<password>           # For passwords
<token>              # For tokens
<request_id>         # For request IDs
<query_id>           # For query IDs
<timestamp>          # For specific timestamps

Example Usage

# ✅ Good - Uses placeholders
snow sql --query "SELECT * FROM snowhouse_import.<deployment>.gs_logs_v WHERE account_id = <account_id>" --format=JSON --connection snowhouse

# ❌ Bad - Real values
snow sql --query "SELECT * FROM snowhouse_import.prod3.gs_logs_v WHERE account_id = 123456" --format=JSON --connection snowhouse

📝 Patterns for Rules

Environment Variable Pattern

# Good - Using environment variables
export SNOW_ACCOUNT="<your_account>"
export SNOW_USER="<your_user>"
export SNOW_PASSWORD="<your_password>"

# Use in commands
snow connection add \
  --name default \
  --account $SNOW_ACCOUNT \
  --user $SNOW_USER \
  --password $SNOW_PASSWORD

Read the full file on GitHub · 287 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. 5d ago First seen · 287 lines · 1,961 tokens per session scan A 413b3b835dc0

Subscribe to this mod's changes

14-security-secrets 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,961 tokens to every session, about $0.0098 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.