secret-scanning-investigator

Validate GitHub secret-scanning alerts against commit history and generate structured security reports.

2|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/swannysec/robot-tools --skill secret-scanning-investigator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: secret-scanning-investigator
Source: https://github.com/swannysec/robot-tools/tree/main/security-toolkit/skills/secret-scanning-investigator
Command: npx skills add https://github.com/swannysec/robot-tools --skill secret-scanning-investigator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

## What problem does it solve? This skill enables security teams to systematically investigate GitHub secret-scanning alerts, trace provenance, assess risk, and generate structured reports suitable for security reviews and dashboards.

## Core Features & Use Cases

  • Evidence-based Investigation: Validate findings by correlating GitHub API data, commit history, and alert details.
  • Parallel Analysis Workflow: Leverage coordinated sub-agents to accelerate alert processing and reporting.
  • Comprehensive Reporting: Produce executive summaries, timelines, and risk assessments for security teams and auditors.
  • Use Case: When a security team triages multiple secret alerts in a repo and requires a unified report for incident response.

### Quick Start Provide a repository identifier and the alert number to initiate the investigation. The skill will fetch alert data, clone the repository into a temporary workspace, run parallel analyses, and generate a structured security report including provenance, timelines, and risk assessment.

Frequently Asked Questions about secret-scanning-investigator

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

FAQPage Schema
How do I investigate GitHub secret-scanning alerts and generate a security report?

To investigate GitHub secret-scanning alerts, provide a repository identifier and alert number to fetch alert data, validate findings against commit history, and generate a structured security report with provenance and risk assessment.

What is the best way to triage multiple secret-scanning alerts for incident response?

Triage multiple secret-scanning alerts by running a parallel analysis workflow that correlates GitHub API data with commit history, producing a unified report with executive summaries and timelines for security teams.

How does validating secret scan findings against commit history work?

Validating secret scan findings works by fetching GitHub API alert details, cloning the repository into a temporary workspace, and correlating alert data with commit history and content to trace provenance and assess risk.

Can I use this to produce structured reports suitable for security dashboards and auditors?

Yes, you can use this to produce structured security reports that include comprehensive timelines, provenance data, and risk assessments suitable for security dashboards, reviews, and auditors.

What do I need to provide to start a GitHub secret-scanning investigation?

To start a GitHub secret-scanning investigation, you need to provide a repository identifier and the specific alert number to initiate the fetching, cloning, and parallel analysis processes.