proton

Scan files and piped data for API keys and credentials using pattern-based rules.

235|25|Updated May 7, 2026
One-click install
npx skills add https://github.com/chainreactors/aiscan --skill proton
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: proton
Source: https://github.com/chainreactors/aiscan/tree/main/skills/proton
Command: npx skills add https://github.com/chainreactors/aiscan --skill proton

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Proton addresses the critical security risk of accidentally committing or exposing sensitive information like API keys, database credentials, and private keys within project files or data streams.

Core Features & Use Cases

  • Pattern-Based Scanning: Utilizes a robust library of over 156 built-in rules to identify secrets using nuclei-style template matching.
  • Flexible Input Handling: Scans local directories, individual files, or live data piped from other shell commands.
  • Customizable Filtering: Allows users to filter findings by severity, specific rule IDs, or custom regex patterns to reduce noise and focus on high-risk vulnerabilities.

Quick Start

Use the proton skill to scan the current directory for high-severity secrets and output the findings in JSON format.

Frequently Asked Questions about proton

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

FAQPage Schema
How do I scan files for exposed API keys and credentials?

You can scan local directories, individual files, or piped data streams for secrets using pattern-based matching. It applies over 156 built-in rules to identify API keys, tokens, and credentials during security auditing or vulnerability assessments.

What is secret leakage detection in source code?

Secret leakage detection identifies sensitive information like API keys, database credentials, and private keys within project files. It uses pattern-based matching with template rules to prevent accidental exposure of credentials in code repositories or data streams.

Can I filter secret scanning results by severity to reduce noise?

Yes, you can filter scanning findings by severity, specific rule IDs, or custom regex patterns. This customizable filtering reduces noise and helps focus vulnerability assessments on high-risk credentials and tokens identified during the scan.

Does the secret scanner support live data piped from shell commands?

Yes, the scanner supports live data piped from other shell commands alongside local directories and individual files. It uses template-based rule sets to perform high-precision secret scanning across these diverse input environments.

Do I need custom template rules to detect credentials in diverse file types?

You do not need custom rules to start; over 156 built-in rules provide high-precision scanning across diverse file types. However, customizable regex patterns and filtering allow you to refine detection for specific requirements.

How do I output secret scanning findings in JSON format?

You can output scanning findings in JSON format after running the scanner against your target directory or data stream. This structured output integrates with automated vulnerability assessment workflows for further analysis.