skills.rest
Open330
Open330OFFICIAL
Explore all skills by this author →
WebsiteGitHub

auditing-security

Detect secrets and credentials in code and Git history.

1|Updated Feb 19, 2026
Search Tags:#security#credentials#git-history#secrets-detection#repository-audit#code-security
One-click install
npx skills add https://github.com/Open330/agt --skill auditing-security-open330
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: auditing-security
Source: https://github.com/Open330/agt/tree/main/security/security-auditor
Command: npx skills add https://github.com/Open330/agt --skill auditing-security-open330

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Audits repository security by analyzing current code and commit history for sensitive information leaks. Detects API keys, passwords, and credentials to prevent data exposure.

Core Features & Use Cases

  • Detects secrets such as API keys, credentials, and sensitive strings across code and history.
  • Inspects Git history for previously committed secrets and flags risky patterns.
  • Verifies basic safeguards like .gitignore coverage to reduce leakage risk.

Quick Start

Run a full security audit with the security-audit.sh script by executing security-audit.sh scan in the repository.

Frequently Asked Questions about auditing-security

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I scan my repository for exposed secrets in Git history?▼

Secrets detection in Git history works by applying static analysis with grep-based patterns to scan commits and current code for sensitive strings like API keys and passwords. It flags risky patterns to prevent data exposure.

How do I check if my .gitignore properly protects sensitive files?▼

To run a full repository security audit, execute the security-audit.sh script with the scan argument in your project directory. This initiates static analysis to examine code, commit history, and .gitignore configurations.

Can I use this secrets detection script in a CI pipeline?▼

Yes, this repository audit is designed for CI pipelines, code reviews, and compliance checks. It applies to any software project with Git history where security hygiene matters, enabling periodic automated scans.

Do I need any external dependencies to run a code security audit?▼

No external dependencies are required. The repository audit uses a Bash script and grep-based patterns to perform static analysis, detecting secrets directly without needing additional security tools or packages.

What types of credentials and secrets can repository auditing detect?▼

The repository audit detects API keys, passwords, credentials, and sensitive strings across current code and Git history. It uses grep-based patterns to flag risky data exposure patterns and prevent leaks.

Related Skills

Explore More Software Engineering Skills→
d0whc3rd0whc3r
2

speckit-git-initialize

Initialize a Git repository and create an initial commit.

Community
Intermediate
jamesjlundinjamesjlundin
32

secrets-scanner

Scan codebases for secrets, credentials, and PII patterns.

Community
Intermediate
yonyon
3

lint

Run linters and static analysis tools with severity-based output and auto-fix mode.

Community
Basic
cwinvestmentscwinvestments
412

memstack-security-secrets-scanner

Scan source code and git history for hardcoded secrets and leaked API keys.

Community
Intermediate