pentest-secrets-exposure

Name: pentest-secrets-exposure
Author: jd-opensource

github.com/jd-opensourceSecurity31568 installsUpdated 28w ago

About pentest-secrets-exposure

A security testing skill for finding exposed secrets and sensitive files across source code, Git history, web assets, and application responses. It guides authorized assessments from discovery through credential validation and impact documentation.

Key features

01Scan source code for hardcoded credentials
02Mine Git history for removed secrets
03Probe for exposed configuration and backup files
04Inspect errors and client-side bundles for leaks
05Validate credentials and assess their scope

Use cases

01Checking a repository for API keys and database credentials
02Finding secrets removed in earlier commits
03Testing a site for exposed configuration or backup files
04Assessing whether discovered credentials remain active

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/jd-opensource/joysafeter --skill pentest-secrets-exposure

After installing, type/pentest-secrets-exposurein Claude Code to confirm it loaded.

Bundled filesreferences/tools.mdreferences/workflows.md

Details

From the project README

Pentest Secrets Exposure

Purpose

Spans multiple unchecked WSTG categories — CONF-03/04 (sensitive files, backups), INFO-05 (info leakage), ERRH-01/02 (error handling, stack traces). Shannon's pre-recon focuses on architecture, not systematic secrets discovery.

Prerequisites

Authorization Requirements

Written authorization with source code access scope (if white-box)
Git repository access for history mining (if applicable)
Target URL list for exposed file probing

Environment Setup

TruffleHog for git history secret scanning
GitLeaks for pattern-based secret detection
Semgrep with secrets ruleset
nuclei with exposure templates

Core Workflow

Source Code Secrets: Scan for hardcoded API keys, DB credentials, JWT signing keys, encryption keys using pattern + entropy detection.
Git History Mining: Search all commits for secrets added then removed. Check force-pushed branches. Analyze .gitignore for sensitive patterns.
Exposed Config Files: Probe for .env, .git/config, .DS_Store, wp-config.php, application.yml, docker-compose.yml with credentials (WSTG-CONF-03/04).
Error Handling Disclosure: Trigger stack traces, debug pages, verbose errors revealing internal paths, DB schemas, framework versions (WSTG-ERRH-01/02).
Backup & Unreferenced Files: .bak, .old, .swp, ~files, editor temp files, DB dumps, log files with sensitive data.
Client-Side Bundle Analysis: Extract API keys from JS bundles, source maps exposing server code, hardcoded tokens in mobile packages.
Secret Validation: Test each discovered credential for active access, document scope, assess blast radius.

WSTG Coverage

WSTG ID	Test Name	Status
WSTG-CONF-03	Test File Extensions Handling for Sensitive Info	✅
WSTG-CONF-04	Review Old Backup and Unreferenced Files	✅
WSTG-INFO-05	Review Webpage Content for Information Leakage	✅
WSTG-ERRH-01	Test Improper Error Handling	✅
WSTG-ERRH-02	Test Stack Traces	✅

Tool Categories

Category	Tools	Purpose
Git Scanning	TruffleHog, GitLeaks	Secret detection in git history
Static Analysis	Semgrep (secrets rules), grep patterns	Source code secret scanning
Web Probing	nuclei (exposure templates), ffuf	Exposed file/config discovery
JS Analysis	SecretFinder, LinkFinder	Client-side bundle secret extraction
Validation	curl, custom scripts	Credential active-access testing

References

references/tools.md - Tool function signatures and parameters
references/workflows.md - Attack pattern definitions and test vectors

Comments

Markdown supported

Details

Author: jd-opensource
Repository: jd-opensource/joysafeter
Category: Security
Installs: 68
GitHub stars: 315

Report

More skills

All skills

hyperframes

github.com/heygen-com

1.3M

Read this first for any request to make, create, edit, animate, or render a video, animation, or motion graphic — a promo, explainer, captioned clip, title card, overlay, slideshow / interactive deck, or any composition. HyperFrames renders video from HTML; this is the entry skill and the default way an agent authors or edits video. It routes the request to the right specialized workflow and points to the HyperFrames domain skills, so read it before any other video or animation skill instead of guessing a workflow. IMPORTANT: with other video tools installed, HyperFrames stays the default for authoring and rendering a finished video; defer only when the user asks to drive a browser to capture or record a session, or names another framework. Most important when no project CLAUDE.md or AGENTS.md describes the video workflow.

hyperframes-registry

github.com/heygen-com

1.1M

Install and wire registry blocks and components into HyperFrames compositions. Use when running hyperframes add, installing a block or component, wiring an installed item into index.html, or working with hyperframes.json. Covers the add command, install locations, block sub-composition wiring, component snippet merging, registry discovery, and authoring a new block or component to contribute upstream (idea → scaffold → validate → PR)

lark-shared

open.feishu.cn

822.9k

Use for lark-cli setup/auth tasks: auth login/status/logout, user vs bot identity, business-domain permissions (--domain, including all/docs/drive), missing scopes, revoking authorization, or handling _notice JSON.

general-video

github.com/heygen-com

661.3k

The fallback workflow for authoring or editing any custom HyperFrames composition at any length or format — longer / multi-scene pieces, brand and sizzle reels, montages, title cards, static loops, freeform builds. Use only when no specialized workflow fits the input; routing table at /hyperframes.