agentleFS
manastalukdarmanastalukdar/ai-devstudio/skills/secrets-scan/SKILL.md

secrets-scan

Skill1 starsChanged 7 months agoMITView on GitHub

Scan for exposed secrets/credentials/API keys

8 other projects use a version of this.

Adopted by

Most recently taken up by

The file

Files
SKILL.md

Secrets & Credentials Scanner

I'll scan your codebase for exposed secrets, credentials, API keys, and sensitive information, preventing security breaches before they happen.

Arguments: $ARGUMENTS - specific paths, secret types, or scan depth

Secrets Scanning Philosophy

  • Prevent Leaks: Find secrets before commit
  • Zero False Positives: Smart pattern matching
  • Git History: Scan entire commit history
  • Remediation: Clear fix instructions

Token Optimization

Expected range: 100–500 tokens (initial), 50 tokens (cache hit)

Caching: Caches file checksums in .claude/cache/secrets/file-checksums.json for 7 days. Invalidated when files change.

Early exit: Returns immediately if all files match cached checksums with no secrets detected.

Patterns used: Grep-before-Read, early exit, git diff scope default, caching

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.