agentleFS
Sign inStart free
bordenetbordenet/superpowers-plus/.cursor/rules/security.mdc

superpowers-plus / rules

Cursor rule8 starsChanged 3 days agoMITView on GitHub

security rules

  • Reads credentials

The file

We split this security.mdc into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Distinctive:

    Scan: - Run security scanners

    line 34
  2. Distinctive:

    NEVER commit secrets to git

    line 51
  3. Distinctive:

    Use environment variables for API keys

    line 52
  4. Very specific:

    Use .env.local files (gitignored)

    line 54

≈ “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
security.mdc
---
description: security rules
alwaysApply: true
---

# Security Workflow

> **Priority**: CRITICAL - a leaked secret is not fixed by rewriting the sentence later.  
> **Source**: codebase-reviewer, scripts AGENTS.md, security-upgrade skill

## 🔒 Pre-Commit Hooks - NEVER BYPASS

Pre-commit hooks exist to protect intellectual property. **NEVER disable or bypass them.**

```bash
# ❌ NEVER DO THIS
git commit --no-verify

# ✅ ALWAYS DO THIS
git commit  # Let hooks run
```

## Security Scanning Tools

| Language | Tool | Command |
|----------|------|---------|
| Node.js | npm audit | `npm audit --json` |
| Go | govulncheck | `govulncheck ./...` |
| Python | pip-audit | `pip-audit -r requirements.txt` |

## Security Upgrade Workflow

1. **Discovery** - Identify projects with dependencies
2. **Scan** - Run security scanners
3. **Upgrade** - Fix vulnerabilities
4. **Validate** - Compile, test, verify
5. **Re-scan** - Confirm fixes
6. **Commit** - Push with green CI

## CVE Response Priority

| Severity | Response Time |
|----------|---------------|
| Critical | Immediate |
| High | Same day |
| Moderate | Within week |
| Low | Next release |

## Secret Management

- NEVER commit secrets to git
- Use environment variables for API keys
- Store secrets in secure credential managers
- Use `.env.local` files (gitignored)
- Prompt for secrets interactively in setup scripts

## Related Skills

For comprehensive security workflows:
- `superpowers-plus/skills/security-upgrade/`


<!-- golden-agents:generated -->

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