security-basics
Skill1 starsChanged 3 months agoMITView on GitHub
When a repo is about to be public or the user wants baseline security. Triggers: 'security', 'SECURITY.md', 'dependabot', 'am I leaking secrets', 'security basics'. Adds a disclosure policy, dependency and secret scanning, and checks nothing sensitive is committed.
- Reads credentials
2 other projects use a version of this.
Adopted by
Most recently taken up by
- lukashouthoofd/cenekathontheir own version, first seen Nov 8, 2026
- timothy-pham/copilot-suitetheir own version, first seen Mar 17, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- lukashouthoofd/cenekathon★ 1same name
- timothy-pham/copilot-suite★ 0same 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 repository16 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- add-testsSkill
- cut-a-releaseSkill
- env-and-configSkill
- license-and-legalSkill
- lint-and-formatSkill
- one-command-runSkill
- package-for-npmSkill
- package-for-pypiSkill
- readme-that-convertsSkill
- repo-hygiene-passSkill
- set-up-ciSkill
- ship-checklistSkill
- ship-contextSkill
- write-a-changelogSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
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
- Very specific: line 26
No secrets in the repo or history, .env.example present, SECURITY.md exists, and dependency and secret scanning are on.
≈ “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
Security Basics
Baseline hygiene so a public repo does not embarrass you. Not a full audit, the essentials.
Before you start
Read .agents/ship.md.
Steps
- Check for committed secrets (grep history for keys and tokens, scan with a tool). If found, rotate them and remove from history; a
.envin git is a leak even if later deleted. - Add
.env.examplewith placeholder keys and no real values; ensure.envis gitignored. Seeenv-and-config. - Add
SECURITY.mdwith how to report a vulnerability (an email or a private advisory) and a supported-versions line. - Turn on scanning: Dependabot or renovate for deps, secret scanning, and private vulnerability reporting on GitHub.
- Least privilege: CI tokens and any bot use the minimum scope.
Done when
No secrets in the repo or history, .env.example present, SECURITY.md exists, and dependency and secret scanning are on.
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.