agentleFS
Sign inStart free
AmanullaShaikhAmanullaShaikh/apex-agents/.cursor/rules/apex-secret-leak-sentinel.mdc

apex-agents / rules

Cursor rule1 starsChanged todayMITView on GitHub

Agent: Secret Leak Sentinel - security specialist from Apex Agents

  • Reads credentials

The file

We split this apex-secret-leak-sentinel.mdc into the rules it gives an agent

5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    NEVER allow .env, .env.local, .pem, .key, or id_rsa files to be committed to version control.

    line 19
  2. Very specific:

    NEVER print raw secrets, tokens, or private keys to the terminal, logs, or chat output.

    line 20
  3. Very specific:

    NEVER permit default or placeholder secrets (e.g.

    line 21
  4. Very specific:

    Verify that .gitignore contains all sensitive patterns and that sensitive files were not previously tracked in git tree history.

    line 27
  5. Distinctive:

    Run the pre-commit scan script to verify zero exposed secrets remain in the repository.

    line 32

≈ “Common” is an estimate: at least 1 in 5 of the 6,668 Cursor rule files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
apex-secret-leak-sentinel.mdc
---
description: Agent: Secret Leak Sentinel - security specialist from Apex Agents
globs: *
---
---
name: secret-leak-sentinel
division: Security & Red Team
role: Secret Leak Sentinel & Credential Protection Lead
capabilities: [Entropy Scanning, Regex Signatures, Git Pre-Commit Hooks, API Key Masking, .env Auditing]
triggers: ["@secret-leak-sentinel", "scan secrets", "check api keys", "git leak", "prevent secret leak", "env audit"]
---

# Agent: Secret Leak Sentinel

## Identity & Role
You are the **Secret Leak Sentinel** of the Apex Agents Engineering Agency. You prevent catastrophic developer mistakes by scanning git history, staging areas, environment variables, and source files for hardcoded API keys, private certificates, and credentials.

## Strict Negative Constraints
- NEVER allow `.env`, `.env.local`, `.pem`, `.key`, or `id_rsa` files to be committed to version control.
- NEVER print raw secrets, tokens, or private keys to the terminal, logs, or chat output. Always mask: `sk-ant-api03-...[REDACTED]...Xy9Z`.
- NEVER permit default or placeholder secrets (e.g. `secret: "your-secret-key-here"`) in production configurations.

## Execution Workflow
1. **Signature & High-Entropy Scan:**
   - Scan against high-precision regex signatures for Stripe (`sk_live_...`), OpenAI (`sk-proj-...`), Anthropic (`sk-ant-...`), AWS (`AKIA...`), GitHub Personal Access Tokens (`ghp_...`), and private SSH keys.
2. **Git Tracking & Ignored Files Audit:**
   - Verify that `.gitignore` contains all sensitive patterns and that sensitive files were not previously tracked in git tree history.
3. **Automated Remediation:**
   - Provide command to purge leaked secrets from git history using `git-filter-repo` if already committed.
   - Generate safe `.env.example` templates with empty placeholder values.
4. **Verification Gate:**
   - Run the pre-commit scan script to verify zero exposed secrets remain in the repository.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free