security-scan

Detect secrets and credentials in source code and configuration files.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/JcgGOs/fulong --skill security-scan-jcggos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-scan
Source: https://github.com/JcgGOs/fulong/tree/main/skills/security-scan
Command: npx skills add https://github.com/JcgGOs/fulong --skill security-scan-jcggos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detects secrets and sensitive credentials in source code and configuration.

Core Features & Use Cases

  • Pre-commit and code-review guard to prevent leaking tokens, keys, passwords, and other credentials
  • Git history and config-file audit to catch secrets before they are committed
  • Remediation guidance with best practices to rotate and ignore secrets

Quick Start

Run a pre-commit style scan to detect tokens, API keys, and passwords in your repository and surface them for remediation.

Frequently Asked Questions about security-scan

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

FAQPage Schema
How do I detect secrets and API keys in source code before committing?

Detecting secrets in source code involves scanning files for sensitive credentials like API keys and tokens. This Skill performs pre-commit checks and repository audits to identify exposed secrets and provide remediation guidance before they are committed.

Can I scan git history for leaked credentials and passwords?

Yes, scanning git history for leaked credentials investigates past commits to find embedded passwords and tokens. This Skill performs git history investigations to catch secrets that may have been committed previously, surfacing them for remediation.

What is a pre-commit check for credential leaks?

A pre-commit check for credential leaks scans staged source code and configuration files to block sensitive tokens from entering the repository. It applies pattern scans to identify API keys, passwords, and other secrets before they are committed.

How do I audit configuration files for sensitive credentials?

Auditing configuration files for sensitive credentials involves scanning them for hardcoded tokens and passwords. This Skill performs configuration file audits to identify secrets, guarding against accidental credential leaks in your repository.

What should I do after finding exposed API keys during a code review?

After finding exposed API keys during a code review, you should follow remediation guidance to rotate and ignore the secrets. This Skill identifies tokens and provides best practices to remediate detected credential leaks.