secrets

A local scanner that looks through a working directory for exposed secrets such as API keys, private keys, database credentials, and hardcoded tokens.

In plain words
What is it for?
Use it to inspect environment files, key files, cloud credential files, and source code for possible credential leaks.
Why use it?
It helps find credentials accidentally committed to project files while keeping the actual secret values hidden in its output.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/rad-security/claude-code-plugin/secrets
Any agent
npx skills add rad-security/claude-code-plugin --skill secrets
Clone the repo
git clone --depth 1 https://github.com/rad-security/claude-code-plugin

Made for: Claude Code, Codex.

Per session 50 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,519 The whole file, excluding the scripts and references it only reads on demand.
Security scan E 2 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00050 $0.01519
Opus 5 $0.00025 $0.00759
Sonnet 5 $0.00010 $0.00304
Haiku 4.5 $0.00005 $0.00152

Measured yesterday against content hash 8dc61e809f0e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade E, and why

secrets scanned grade E with 2 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Enumerates the file system for secretshighData exfiltration

Searching home directories for .env, .ssh, .aws or credential files is reconnaissance for credential theft.

## Step 1: Find Secret Files

Reaches for credential fileshighPrivilege escalation

SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.

find . -maxdepth 5 -type f \( -name "credentials" -o -name "credentials.json" -o -name "service-account*.json" -o -name "application_default_credentials.json" \) ! -path "*/node_modules/*" ! -path "*/.git/*" 2>/dev/null
plugins/agentkeeper/skills/secrets/SKILL.md · 163 lines

How it starts

The opening of the file, as written. The whole thing — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AgentKeeper Secret Scanner

You are scanning the current working directory for exposed secrets. This runs entirely locally — no network calls.

CRITICAL: NEVER print, display, or echo actual secret values. Show only the file path, line number, pattern type, and a masked preview.

Step 1: Find Secret Files

Use Glob and Bash to locate files that commonly contain secrets:

Environment files

find . -maxdepth 5 -type f \( -name ".env" -o -name ".env.*" -o -name ".env.local" -o -name ".env.production" -o -name ".env.development" \) ! -path "*/node_modules/*" ! -path "*/.git/*" 2>/dev/null

Private key files

find . -maxdepth 5 -type f \( -name "*.pem" -o -name "*.key" -o -name "*.p12" -o -name "*.pfx" -o -name "id_rsa" -o -name "id_ed25519" -o -name "id_ecdsa" -o -name "*.keystore" \) ! -path "*/node_modules/*" ! -path "*/.git/*" 2>/dev/null

Cloud credential files

find . -maxdepth 5 -type f \( -name "credentials" -o -name "credentials.json" -o -name "service-account*.json" -o -name "application_default_credentials.json" \) ! -path "*/node_modules/*" ! -path "*/.git/*" 2>/dev/null

Step 2: Scan Source Files for Secret Patterns

Use Grep to search for secret patterns in source code files. Search in common source file extensions only (to avoid binaries). For each pattern, collect file path, line number, and the pattern type.

AWS Access Keys

AKIA[0-9A-Z]{16}

AWS Secret Keys

(?i)(aws_secret_access_key|aws_secret_key)\s*[=:]\s*\S+

Stripe Keys

(sk_live_|rk_live_|sk_test_|rk_test_)[a-zA-Z0-9]{20,}

GitHub Tokens

(ghp_|gho_|ghu_|ghs_|ghr_)[a-zA-Z0-9]{36,}

Generic API Key Patterns

(?i)(api[_-]?key|apikey|api[_-]?secret)\s*[=:]\s*['"][a-zA-Z0-9_\-]{20,}['"]

Private Key Headers

-----BEGIN (RSA |EC |DSA |OPENSSH )?PRIVATE KEY-----

Database Connection Strings

(?i)(mongodb|postgres|postgresql|mysql|redis|amqp):\/\/[^\s'"]+:[^\s'"]+@

JWT Tokens (hardcoded)

eyJ[a-zA-Z0-9_-]{10,}\.eyJ[a-zA-Z0-9_-]{10,}\.[a-zA-Z0-9_-]+

Read the full file on GitHub · 163 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 163 lines · 50 tokens per session scan E 8dc61e809f0e

Subscribe to this mod's changes

secrets is a skill published in the GitHub repository rad-security/claude-code-plugin (2 stars, last pushed 26d ago), licensed MIT. It adds 50 tokens to every session and 1,519 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it E with 2 findings (enumerates the file system for secrets, reaches for credential files). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens