Skip to content
TrustedSkillsbeta
Back to all skills

Code Hardcode Audit

Checked
terrylica·vlatest·security·MIT

Identifies potential security vulnerabilities and hardcoded secrets within codebases using advanced pattern recognition techniques.

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 terrylica/cc-skills --skill code-hardcode-audit -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

terrylica

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

    Only contacts known or declared hosts: json-schema.org.

    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

    json-schema.orgstandards

  • 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 terrylica/cc-skills at 3a1dc29965.

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

Commit
3a1dc29965
Manifest
plugins/itp/skills/code-hardcode-audit/SKILL.md
Scanned
22 files, 3,195 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 code-hardcode-audit skill scans source code repositories to identify hardcoded secrets, API keys, and sensitive credentials that pose security risks. It analyzes files across a project directory to detect patterns matching common secret formats and reports their locations for remediation.

When to use it

  • Before deploying an application to production to ensure no accidental secrets were committed to version control.
  • During code reviews when integrating third-party libraries or dependencies that might contain exposed keys.
  • After cloning a legacy repository to audit existing infrastructure configurations for compromised credentials.
  • As part of a continuous integration pipeline to block merges containing detected sensitive data.

Key capabilities

  • Recursively scans entire project directories for hardcoded values.
  • Identifies common secret patterns such as API keys, passwords, and tokens.
  • Provides specific file paths and line numbers where secrets are found.
  • Supports various programming languages and configuration formats.

Example prompts

  • "Run a full audit on my current project directory to find any hardcoded AWS access keys."
  • "Scan the config folder for exposed database passwords or API tokens."
  • "Audit this repository for secrets before I merge the latest feature branch."

Tips & gotchas

Ensure you exclude sensitive files from your scan if they are intentionally stored in plaintext, as the tool will flag them. Always review the generated report manually to confirm false positives and prioritize critical findings like production database credentials.