Skip to content
TrustedSkillsbeta
Back to all skills

Git Security Checks

Listed
laurigates·vlatest·backend·MIT

Helps with Git, security as part of implementing security and authentication workflows.

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 laurigates/claude-plugins --skill git-security-checks -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

laurigates

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 credential access: failed

    Touches credential material in 2 places.

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

    What it found

    • git-plugin/skills/git-security-checks/scripts/security-scan.sh:63SSH private keys or config
      "id_rsa"
    • git-plugin/skills/git-security-checks/scripts/security-scan.sh:64SSH private keys or config
      "id_ed25519"

  • 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 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 laurigates/claude-plugins at 45d1d7dcf6.

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

Commit
45d1d7dcf6
Manifest
git-plugin/skills/git-security-checks/SKILL.md
Scanned
3 files, 633 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 performs automated security analysis on Git repositories to identify vulnerabilities and misconfigurations before code is committed or pushed. It scans for exposed secrets, insecure dependencies, and dangerous patterns within the repository history and current state.

When to use it

  • Before pushing sensitive credentials like API keys or tokens to a public or private branch.
  • During pre-commit workflows to prevent accidental exposure of private data in version control.
  • When auditing third-party open-source dependencies for known security flaws.
  • As part of a CI/CD pipeline to enforce security standards before merging pull requests.

Key capabilities

  • Detects hardcoded secrets and sensitive information within code files.
  • Identifies insecure or vulnerable software dependencies in the project.
  • Analyzes Git history to find previously committed sensitive data that may have been deleted but remains accessible.
  • Flags common security misconfigurations in repository settings and file permissions.

Example prompts

  • "Run a full security scan on my current branch to check for exposed API keys or database passwords."
  • "Analyze the last 50 commits to see if any sensitive files were accidentally committed and not properly removed from history."
  • "Check our package.json and requirements.txt files for known vulnerable dependencies before I merge this PR."

Tips & gotchas

Ensure your repository is cloned locally or accessible via a secure connection, as the tool needs to read file contents and commit logs. While effective at finding obvious secrets, it may not catch every complex logic vulnerability; always pair this with manual code reviews for critical security features.