skills.rest
jbovet
jbovetCOMMUNITY
Explore all skills by this author →
Website𝕏@josebovetGitHub

secrets-skill

Scan code and configuration files for leaked credentials and tokens.

3|Updated Feb 26, 2026
Search Tags:#security#secrets#credentials#ci-cd#scanning#gitleaks#exposure
One-click install
npx skills add https://github.com/jbovet/oxidized-agentic-audit --skill secrets-skill
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: secrets-skill
Source: https://github.com/jbovet/oxidized-agentic-audit/tree/main/tests/fixtures/secrets-skill
Command: npx skills add https://github.com/jbovet/oxidized-agentic-audit --skill secrets-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Leaked credentials in repositories and scripts create security risks; this Skill provides a testbed to validate secrets scanning tooling and detection rules.

Core Features & Use Cases

  • Secrets detection in code and config files to surface exposed keys and tokens
  • CI/CD integration testing with gitleaks-like patterns
  • Use case: verify leaked credentials are detected and flagged in sample workflows

Quick Start

Scan a repository containing leaked keys to verify gitleaks integration during CI checks.

Frequently Asked Questions about secrets-skill

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

FAQPage Schema
How do I detect leaked credentials in code and configuration files?▼

Detect leaked credentials by scanning code, configuration files, and scripts for sensitive keys and tokens using configurable rules. This process surfaces exposed secrets across varied project structures and multiple languages.

Can I test secrets scanning integration in my CI/CD pipelines?▼

Yes, you can test secrets scanning in CI/CD pipelines using gitleaks-like patterns to verify leaked credentials are detected and flagged during continuous integration checks.

How do I scan a repository for exposed keys and tokens?▼

Scan a repository for exposed keys and tokens by applying organization-specific secret patterns and configurable detection rules to identify sensitive data across multiple languages and scripts.

Do I need custom rules to scan for sensitive keys in scripts?▼

Yes, you need organization-specific secret patterns and configurable rules to tailor detection to your security policy and accurately identify sensitive keys in scripts.

What is the best way to validate secrets scanning tooling for repositories?▼

Validate secrets scanning tooling by using a testbed repository containing leaked keys to verify that detection rules and gitleaks integration correctly surface exposed credentials during checks.

Why are leaked credentials in repositories a security risk?▼

Leaked credentials in repositories and scripts create security risks because exposed keys and tokens can be exploited; scanning tooling validates detection rules to prevent this exposure.

Related Skills

Explore More Legal & Compliance Skills→
riandeoliveirariandeoliveira

implementing-secret-scanning-with-gitleaks

Scan Git repositories with Gitleaks to detect and prevent hardcoded credentials.

Community
Advanced
ongspxmongspxm
1

meagent-update-blog

Trigger and monitor GitLab CI/CD pipelines for blog content rendering.

Community
Intermediate
balsm-healthbalsm-health
2

implementing-secrets-scanning-in-ci-cd

Automate hardcoded secret detection in CI/CD pipelines with gitleaks and trufflehog.

Official
Advanced
mpauloskympaulosky

secret-handling

Block commits containing detected secrets and forbid reading live .env files.

Community
Advanced