secrets-scanner

Detect leaked credentials in source code with configurable secret patterns.

Updated Jan 21, 2026
One-click install
npx skills add https://github.com/vecear/Nipponverb --skill secrets-scanner-vecear
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: secrets-scanner
Source: https://github.com/vecear/Nipponverb/tree/main/.claude/skills/secrets-scanner
Command: npx skills add https://github.com/vecear/Nipponverb --skill secrets-scanner-vecear

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detects leaked credentials in codebases and helps prevent exposure by adding structured checks and remediation workflows.

Core Features & Use Cases

  • Pre-commit hooks for secret detection
  • CI integration with scanning rules and remediation steps
  • Custom secret scanner and guidance for implementing secret management

Quick Start

Install pre-commit hooks and run the scanner on your repository to detect secrets before committing.

Frequently Asked Questions about secrets-scanner

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

FAQPage Schema
How do I detect leaked credentials in source code before committing?

Set up CI pipeline secret scanning by integrating configurable scanning rules and remediation steps. This automates the detection of leaked credentials during continuous integration, alerting on exposed API keys and tokens before deployment.

Can I configure custom secret patterns for my API keys and tokens?

Integrate GitHub secret scanning with environment validation and monitoring to detect leaked credentials. This provides structured checks and remediation workflows, ensuring exposed tokens and keys are caught across your development lifecycle.

What is the best way to add secret scanning and remediation workflows to a CI pipeline?

Add secret scanning to a CI pipeline by integrating scanning rules and structured remediation steps. This approach detects leaked credentials in source code, alerts on potential secret exposures, and guides the implementation of secret management.

Can I use a custom secret scanner script for detecting private keys and tokens?

Yes, you can use a custom secret scanner script to detect private keys and tokens. It supports configurable secret patterns and integrates with pre-commit hooks, CI pipelines, and remediation workflows for comprehensive credential detection.

Does this support GitHub secret scanning integration and environment validation?

Yes, it supports GitHub secret scanning integration points along with environment validation and monitoring. These features help detect leaked credentials in codebases and add structured checks to prevent exposure.