security-secrets
Skill0 starsChanged 16 days agoMITView on GitHub
Audit a repository for exposed credentials, unsafe secret storage, accidental secret logging, environment/configuration mistakes, and credential leakage in generated reports. Use for secret-scanning and secret-management reviews.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- SwastikPandey1024/agentic-engineering-ostheir own version, first seen Oct 20, 2026
- GA14-hub/claude-code-kit-jatheir own version, first seen Feb 13, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- GA14-hub/claude-code-kit-ja★ 1same name
- SwastikPandey1024/agentic-engineering-os★ 1same 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 repository5 other files it gives its agents.
- ai-security-auditSkill
- security-ai-llmSkill
- security-apiSkill
- security-reconSkill
- security-supply-chainSkill
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 15
Never authenticate with a discovered credential, test it against a live service, or transmit it elsewhere.
≈ “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
Secrets Security Audit
Focus on whether credentials can be exposed, misused, committed, logged, or included in audit artifacts. Do not reveal discovered secret values.
Workflow
- Inspect repository history and current tracked files where authorized, including source, configuration, examples, CI workflows, build artifacts, logs, and documentation. Avoid dumping secret values into terminal output or chat.
- Distinguish actual credential candidates from placeholders, examples, public identifiers, and test fixtures. Confirm context and whether the value is tracked or reachable.
- Review environment variable handling, secret-manager integration, client/server boundaries, debug endpoints, error reporting, logging, CI permissions, and generated audit reports.
- Never authenticate with a discovered credential, test it against a live service, or transmit it elsewhere. Report only the file/line, secret type, exposure context, and safe remediation; redact the value.
- Recommend revocation/rotation for likely live credentials, followed by history cleanup only where appropriate and coordinated with repository owners.
- Review report artifacts for accidental secret leakage and make sure redaction happens before display or persistence.
- Record false positives and scope limitations. Treat a match as a candidate until its context and exposure are verified.
References
- Core evidence standard:
../../SKILL.md - Secrets playbook:
../../agents/secrets.md - Configuration playbook:
../../agents/configuration.md - Redaction utilities:
../../lib/util.js - Validation scripts:
../../scripts/validate-findings.js
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.