secret-lint
Skill15 starsChanged 5 months agoMITView on GitHub
Automated secret scanning using secretlint to prevent credential leaks.
In this repository29 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- llms-full.txtllms.txt
- llms.txtllms.txt
- anti-ai-slopSkill
- architecture-diagramSkill
- atomic-commitSkill
- build-rustSkill
- codacySkill
- crates-io-name-checkSkill
- dora-reportSkill
- goap-agentSkill
- harnessSkill
- issue-triageSkill
- lint-rustSkill
- metrics-reporterSkill
- privacy-firstSkill
- release-rustSkill
- reviewing-pull-requestsSkill
- self-fix-loopSkill
- skill-creatorSkill
- skill-evaluatorSkill
- stacked-prsSkill
- task-decompositionSkill
- test-rustSkill
- tokio-performanceSkill
- triz-analysisSkill
- triz-solverSkill
- verify-actionsSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 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.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
Run the following command from the repository root:
≈ “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
Secret Lint Skill
This skill provides automated secret scanning using secretlint.
Usage
Local Scanning
Run the following command from the repository root:
make secrets-lintPre-commit Hook
The skill is integrated into the pre-commit pipeline and will scan modified files before each commit.
CI Integration
The secretlint.yml workflow runs this skill on every push to main and develop branches.
Configuration
.secretlintrc.json: Ruleset configuration (at root)..secretlintignore: Ignore patterns (at root).package.json: Dependencies and scripts (in this folder).
Rationalizations
| Rationalization | Reality |
| "It's only a test secret, so it's fine to commit." | Test secrets can leak patterns or trigger scanner false alarms. Use fixture mocks or ignore rules. |
| "I'll clean up the commit history later." | Once pushed, secrets are compromised. Prevent them from entering git in the first place. |
| "I can bypass pre-commit with --no-verify." | Bypassing pre-commit bypasses secret checks and risks leaking production credentials. |
Red Flags
- Using
--no-verifyto bypass secret scanning - Committing hardcoded credentials or API keys directly to git
- Disabling secretlint rules globally instead of configuring
.secretlintignore
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.