Secrets Management Audit

Use when hunting for exposed secrets and auditing how an app you own manages them — API keys, tokens, passwords, and private keys in source, git history, binaries, logs, config, and CI; plus vaulting, rotation, and least-privilege of the secrets themselves.

49 stars 7 forksGit & Code Review Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add mn-youssef/security-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add mn-youssef/security-skills --skill secrets-management-audit
Manual install
git clone --depth 1 https://github.com/mn-youssef/security-skills.git /tmp/security-skills
mkdir -p ~/.claude/skills
cp -r /tmp/security-skills/skills/secrets-management-audit ~/.claude/skills/secrets-management-audit

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Secrets Management Audit (FIND/FIX — credentials & keys)

## Overview
Leaked secrets are among the fastest paths to compromise — one committed key can hand over a whole
cloud account. This skill finds exposed secrets everywhere they hide and audits whether the app
manages them properly (vaulted, rotated, scoped).

**Core principle:** A secret in source/history/logs/binary is **already public** — assume
compromised and rotate. Detection without rotation is theater.

## Applies when / Skip when
- **Applies when:** essentially always — every app has secrets/keys/config somewhere (source,
  git history, logs, env, build artifacts, CI).
- **Skip when:** effectively never. Even a static site has API keys, deploy creds, or CI tokens.
- **If genuinely nothing to scan:** say so explicitly — but verify first; "no secrets" is almost
  always "didn't look hard enough."

## ⚠️ Authorization
Your own/authorized repos, artifacts, and infrastructure. If you find a real exposed secret,
treat it as an incident: rotate first, then fix the leak path.

## Where secrets hide (hunt all of these)
| Location | How |
|----------|-----|
| Source code | Scanners + grep for key patterns |
| **Git history** | Secrets deleted from HEAD still live in history — scan all commits |
| Frontend bundles | JS/source maps shipping keys to the browser |
| Mobile binaries | Decompiled APK/IPA (`apktool`/`jadx`, `strings`) |
| Logs & error output | Tokens/PII printed to stdout/log files/APM |
Read the full skill on GitHub

Details

Skill name
secrets-management-audit
Path
skills/secrets-management-audit/SKILL.md
License
MIT
Repo updated
12 June 2026

FAQ

What does the Secrets Management Audit skill do?

Use when hunting for exposed secrets and auditing how an app you own manages them — API keys, tokens, passwords, and private keys in source, git history, binaries, logs, config, and CI; plus vaulting, rotation, and least-privilege of the secrets themselves.

How do I install the Secrets Management Audit skill?

Claude Code plugin: /plugin marketplace add mn-youssef/security-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Secrets Management Audit popular?

It lives in mn-youssef/security-skills, which has 49 GitHub stars and 7 forks.

Related skills

Access Control Testing

49

mn-youssef/security-skills

Use when testing whether users can access data or actions they shouldn't — IDOR/BOLA, horizontal and vertical privilege escalation, multi-tenant isolation, forced browsing, function-level authorization (BFLA), and mass assignment. The #1 cause of real-world breaches.

Testing & QA

Active Pentest

49

mn-youssef/security-skills

Use when you need to actually run security tests against a running application you own or are authorized to test — the shared execution harness for lab/proxy/scanner setup, safe non-destructive execution, and standardized proof-of-concept capture that the find/exploit specialist skills rely on.

Security

API Security Testing

49

mn-youssef/security-skills

Use when testing REST, GraphQL, gRPC, or WebSocket APIs against the OWASP API Security Top 10 — object- and function-level authorization (BOLA/BFLA), excessive data exposure, mass assignment, unrestricted resource consumption, and GraphQL-specific abuse. For apps you own or are authorized to test.

Security

Uw Unity Project Setup

47

devdavv/unity-ai-workflow

Full project initialization wizard from ProjectConfig, including folders, packages, Git, and MCP setup. Use when setting up a new Unity project from scratch, creating the folder structure, or bootstrapping infrastructure. Triggers on requests like "set up a new project", "create folder structure", "initialize the project", or "/uw-cmd-setup-project". Reads ProjectConfig.yaml for all decisions.

Git & Code Review

Neovim Review

49

sodiumjoe/dotfiles

Use when the user invokes /neovim-review for a pull request or a local :Review session in Neovim.

Git & Code Review

History

49

lis186/SourceAtlas

Smart temporal analysis using git history - Hotspots, Coupling, and Recent Contributors

Git & Code Review

Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.