Skip to content
TrustedSkillsbeta
Back to all skills

Pentest Secrets Exposure

Checked
jd-opensource·vlatest·security·Apache-2.0

This skill identifies potential secret exposure risks during penetration tests by analyzing application logs and configurations for leaked credentials.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add jd-opensource/joysafeter --skill pentest-secrets-exposure -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

jd-opensource

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned jd-opensource/joysafeter at 12234a11a9.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
12234a11a9
Manifest
skills/pentest-secrets-exposure/SKILL.md
Scanned
3 files, 134 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill, pentest-secrets-exposure, allows AI agents to identify and extract secrets from various file types commonly used in penetration testing engagements. It can parse files like .env, .bashrc, .zshrc, and configuration files (e.g., YAML, JSON) to locate potential sensitive information such as API keys, passwords, and database credentials. The skill aims to automate the tedious process of manual secret hunting during security assessments.

When to use it

  • Automated Reconnaissance: Quickly scan a compromised server or repository for exposed secrets during an initial penetration test phase.
  • Code Review Assistance: Integrate into code review workflows to automatically flag potential secret exposures in new or modified files.
  • Incident Response: Rapidly identify leaked credentials following a suspected data breach.
  • Configuration Audit: Analyze configuration files across infrastructure for unintentional exposure of sensitive information.

Key capabilities

  • Parses .env, .bashrc, .zshrc files.
  • Supports YAML and JSON file parsing.
  • Identifies API keys, passwords, and database credentials within parsed files.

Example prompts

  • "Find all secrets in this .env file: [file content]"
  • "Scan the contents of /path/to/config.yaml for exposed API keys."
  • "Extract any passwords or usernames from these bash scripts: [script content]"

Tips & gotchas

  • The skill's effectiveness depends on the format and structure of the files being analyzed; complex or obfuscated secrets may not be detected.
  • Ensure the AI agent has appropriate permissions to access and read the target files.