Skip to content
TrustedSkillsbeta
Back to all skills

Ghost Scan Secrets

Listed
ghostsecurity·vlatest·security·Apache-2.0

Ghost Scan Secrets swiftly identifies hidden secrets and vulnerabilities within files, safeguarding sensitive data from unauthorized access.

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 ghostsecurity/skills --skill ghost-scan-secrets -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

ghostsecurity

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 failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.

  • No pipe-to-shell installers: failed

    Runs code fetched at install time in 1 place.

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

    What it found

    • plugins/ghost/skills/scan-secrets/agents/init/agent.md:16remote script piped into a shell
      curl -sfL https://raw.githubusercontent.com/ghostsecurity/poltergeist/main/scripts/install.sh | bash
  • 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

    Only contacts known or declared hosts: raw.githubusercontent.com.

    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.

    Hosts contacted

    raw.githubusercontent.comsource host
  • 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.

  • Pinned to a commit: passed

    Scanned ghostsecurity/skills at 6ea8e3ba66.

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

Scanned
9 files, 835 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

The ghost-scan-secrets skill enables AI agents to actively search for and identify exposed secrets within codebases, configuration files, and deployment environments. It automates the detection of hardcoded credentials, API keys, and sensitive tokens that could compromise system security.

When to use it

  • Before merging pull requests containing new environment variables or database connection strings.
  • During pre-deployment checks to ensure no production secrets were accidentally committed to version control.
  • When auditing legacy repositories for forgotten API keys or authentication tokens left in comments.
  • As part of a continuous integration pipeline to block builds if high-risk secrets are detected.

Key capabilities

  • Scans code repositories for common secret patterns and formats.
  • Identifies hardcoded credentials in configuration files, scripts, and documentation.
  • Flags potential security risks by matching against known secret structures.
  • Provides actionable reports highlighting file locations and severity levels.

Example prompts

  • "Scan this repository for any exposed API keys or database passwords."
  • "Check the latest commit for accidentally committed secrets before I push to production."
  • "Identify all hardcoded authentication tokens in the frontend codebase."

Tips & gotchas

Ensure the skill has appropriate read permissions on the target repositories to avoid false negatives. Regularly update the underlying secret detection patterns to stay ahead of emerging credential formats and obfuscation techniques.