safety-gate
Skill0 starsChanged 7 months agoMITView on GitHub
Use PROACTIVELY before any git commit, push, or publish operation. Scans for secrets, credentials, PII, and validates .gitignore. Blocks dangerous commits with actionable remediation guidance.
- Reads credentials
- Commits and pushes
1 other project uses a version of this.
Adopted by
Most recently taken up by
- mongdang/giroktheir own version, first seen Oct 1, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- mongdang/girok★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository17 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- agent-detectionSkill
- auto-delegationSkill
- bookstackSkill
- delegatorSkill
- faceswapSkill
- git-standardsSkill
- headswapSkill
- health-dashboardSkill
- imageSkill
- motionSkill
- multi-terminalSkill
- project-docsSkill
- quality-gatesSkill
- upscaleSkill
- videoSkill
- web-researchSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 3 are distinctive, and 5 are 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.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 56
Use environment variables: instead: process.env.API_KEY
- Distinctive: line 58
If already committed, use git filter-branch or BFG Repo-Cleaner
- Very specific: line 62
Add the missing entries to .gitignore
- Very specific: line 63
Run git rm --cached <file> for files already tracked
- Very specific: line 64
Consider using a .gitignore generator for your tech stack
- Distinctive: line 68
If the gate blocks a legitimate commit:
- Distinctive: line 69
Use git commit --no-verify to bypass (logged)
- Very specific: line 70
Consider adding the pattern to a .safety-gate-ignore file (future)
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill 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.
Files
Safety Gate
Pre-commit safety scanning for secrets, credentials, and sensitive data.
When This Activates
Automatically via PreToolUse hook on:
git commit— scans staged filesgit push— scans files since last pushgit add -A/git add --all— scans all untracked/modified files
What Gets Scanned
Secrets & API Keys
| Category | Patterns |
| AI API Keys | sk-*, pk-*, ANTHROPIC_API_KEY=, OPENAI_API_KEY= |
| AWS | AKIA* (access key IDs) |
| GitHub | ghp_*, gho_*, github_pat_* |
| Slack | xoxb-*, xoxp-* |
| Private Keys | -----BEGIN.*PRIVATE KEY----- |
| Passwords | password=, passwd=, secret= with literal values |
| Database URLs | postgres://user:pass@, mongodb://user:pass@, mysql://user:pass@ |
Dangerous File Types
| File Type | Action |
.env, .env.* | BLOCK — must be in .gitignore |
*.pem, *.key, *.pfx, *.p12, *.crt | BLOCK — certificates/keys |
id_rsa*, id_ed25519* | BLOCK — SSH keys |
.gitignore Validation
Required entries:
.env— environment files*.pem,*.key— certificatesnode_modules/— dependencies.DS_Store— OS files
Remediation
If a secret is found
- Remove the secret from the file
- Use environment variables instead:
process.env.API_KEY - Rotate the secret — any committed secret is compromised
- If already committed, use
git filter-branchor BFG Repo-Cleaner
If .gitignore is incomplete
- Add the missing entries to
.gitignore - Run
git rm --cached <file>for files already tracked - Consider using a
.gitignoregenerator for your tech stack
False Positives
If the gate blocks a legitimate commit:
- Use
git commit --no-verifyto bypass (logged) - Consider adding the pattern to a
.safety-gate-ignorefile (future)
Exit Codes
| Code | Meaning |
| 0 | Safe — no issues found |
| 2 | BLOCKED — issues found, commit prevented |
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
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.