privacy-scan

Detect secrets, PII, and analytics drift with Gitleaks and Semgrep scans.

1|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/ourchitecture/idp --skill privacy-scan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: privacy-scan
Source: https://github.com/ourchitecture/idp/tree/main/.agents/skills/privacy-scan
Command: npx skills add https://github.com/ourchitecture/idp --skill privacy-scan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Runs privacy-focused scanning to detect exposure of secrets, PII, and analytics drift across repositories, tests, and docs.

Core Features & Use Cases

  • gitleaks filesystem and git-history scans to identify secrets exposure and history leakage.
  • semgrep rules for secrets, PII, and privacy patterns, plus targeted checks for sensitive logging and analytics boundaries.
  • triage-ready report generation with findings, severity, locations, and remediation actions across code, tests, and configurations.

Quick Start

Install pinned tools and run the canonical privacy scan to produce a complete report.

Frequently Asked Questions about privacy-scan

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

FAQPage Schema
How do I scan a repository for secrets and PII exposure using Semgrep and Gitleaks?

Scanning a repository for secrets and PII involves running Gitleaks and Semgrep across your codebase. This Skill orchestrates those tools to identify sensitive data exposures and validate findings with severity categories.

What is the best way to detect sensitive data leakage in git history?

Detecting sensitive data leakage in git history requires enabling the include_history option during your privacy scan. This triggers Gitleaks to perform targeted git history scans alongside standard filesystem checks.

Does privacy scanning work on repositories of any programming language?

Yes, privacy scanning applies to repositories of any language. As long as Semgrep and Gitleaks are used, it identifies sensitive data exposures and misconfigurations across code, tests, and documentation.

Do I need a specific toolchain setup to run privacy scans?

You need a pinned toolchain including go, python, uv, semgrep, and gitleaks to run privacy scans. A Moon or Make orchestrated workflow is required to execute the canonical scanning process.

Can I generate triage-ready reports for detected analytics boundaries and secrets?

Yes, privacy scans generate triage-ready reports for detected analytics boundaries and secrets. These reports include findings, severity, locations, and remediation actions across code, tests, and configurations.